feat(cli): add concore setup autodetect command

[avinxshKD]

Adds concore setup for first-run config.

• Detects installed tools via existing doctor helpers

• Writes concore.tools, concore.sudo, concore.octave

• Supports --dry-run and --force

• No backend behavior changes outside new command

I tested with:

python -m unittest tests.test_setup (pass)

fixes #506

[avinxshKD]

@pradeeban pls look at this :P

[avinxshKD]

@pradeeban you asked about "How close are we to stop calling the Java implementation a "toy?" Good work."

I think Java is no longer in “toy” territory for core protocol behavior. The runtime path is in place and covered with direct Java regression tests for parser + API behavior. Yayy

To close this out fully, I can follow up with:

1. Java test execution in CI, and
2. one end-to-end study example with a Java node.

If that sounds good, I’ll open focused PRs after my exam. love to know more

Also outside the GSoC scope, I’d be happy to keep working on Java improvements during the coding period as time permits. Java support would be valuable to keep as a secondary language path in concore :D

[GREENRAT-K405]

Hello @pradeeban @avinxshKD I had a doubt, I wanted to do similar thing with something like 'concore doctor --fix'
that can automatically write concore.tools in case deps are missing or are not configured.

If the deps are not installed and setup globally, we would require to install them (this would require sudo permissions which is not ideal for commands like doctor, even brew doctor doesn't do this).

But say, if the dependencies are already globally configured, then in that case won't it become unnecessary to setup concore.tools?

Just wanted to have a discussion regarding this.