Feedback on new starter toolkit experience v0.2.0

New UX is pretty cool, I was root causing something in runtime and its definitely much faster to get started. Capturing few observations.

1. Not sure if ordering of --help command can be changed to put create at the top, then dev, deploy, invoke, etc
2. Creating templates with newer version of python, in general customers will get better performance and cold start. Runtime will plan to introduce 3.14 in Q1 for direct code deploy, but till then will be great to default to 3.13 a. Nit: Dependency closure also have impact on cold start, so moving pytest-asyncio and pytest to dev-dependencies will help follow minimal required dependency closure.3. Can we please add adot dependency by default: aws-opentelemetry-distro , without it traces aren't enabled in direct code deploy
3. What is *.egg-info directory?
4. BedrockAgentCoreApp has an inbuilt logger which provides structure info in the log like session id and request id, will be useful to reuse that, compared to defining a new logger.
5. A agentcore dev which syncs with deployed agent will be super useful, because without local container its hard to publish traces, an agent deployed in runtime will automatically get traces. This combined agentcore obs is super useful.
6. How to federate and add more templates? Would be great to add templates for long running agents

Start with the numbered observations, the --help output, and the agentcore dev command, then trace how templates, dependencies, logging, and deployment synchronization are defined. Done would require narrowing these requests into separate, accepted changes with clear scope and validation for each item; no specific files or tests are named.

Written by the indexing model from the issue text.