`dpm new` component version awareness

[samuel-williams-da]

Some templates provided by dpm new need to know the underlying canton/daml versions that are active. For example, the quickstart-java template, which provide a pom.xml file including a dependency to bindings-java (this is standard). Since bindings-java has been moved to canton, this pom file must include the associated canton version, however dpm resolve does not directly* expose component versions, so dpm new cannot deduce this.

*versions can be determined indirectly by reading the component path, which always ends in the version string, however this is hacky and will break for local components, ideally the version is deduced from each components's component.yaml file and provided in resolution.