Use cds info from project access to update package json in cap writers

[kjose90]

#1902

This PR consumes #1947

[changeset-bot]

⚠️ No Changeset found

Latest commit: 3691710

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[kjose90]

Here we add cds watch scripts only in cdsUi5PluginInfo has minimum cds version available, this is set during the prompt phase of the app generation. Question for head less app generation - according to the logic here I simply read from the package.json, is this consistent ??? Is there a better way to cater for this watch script addition for headless app?

[kjose90]

Please refer the updated logic for updating CDS watch scripts in cap-config-writer/src/cap-config-writer/package-json.ts.

For the generation of headless applications, where there's no prompt for cdsUi5Plugin, what's the optimal approach to retrieve the cds version from package.json?

We have a function loadModuleFromProject from project-access which will require pre-installing node modules. - i am not sure if this is the right way, if it could have effects elsewhere, and also considering the overhead associated with exporting this function.

In this PR I am currently re-reading this information from package json using satisfiesMinCdsVersion here

[kjose90]

Closing this PR as it has gone stale. Addressed in #1947