fix(dev): correctly detect DENDRON_RELEASE_VERSION using both marketplace and package.json

[eleweek]

fix(dev): correctly detect DENDRON_RELEASE_VERSION using both marketplace and package.json

Currently it gets it from package.json. The updated version gets the latest version from package.json and the marketplace by running (npx vsce show dendron.nightly --json). It concates both things and uses sort -rn | head -n 1 to select the latest version.

I manually tested the command by running it separately in my shell with various versions in package.json.

Testing

• Write Tests
• Confirm existing tests pass
• Confirm manual testing
• If your tests changes an existing snapshot, make sure that snapshots are updated
• If you are adding a new language feature (graphically visible in VS Code/preview/publishing), make sure that it is included in the test workspace

Docs

• if your change reflects documentation changes, also submit a PR to dendron-site and mention the doc PR link in your current PR

Analytics

• if you are adding analytics related changes, make sure the Telemetry docs are updated

[kevinslin]

its okay to do this as a quick fix. can we add a followup task to introduce a cli method?
we now have the nightly version logic duplicated in here as well as in getIncrementedVerForNightly. we should make it as part of the dev cli

dendron dev get-incremented-ver-for-nightly

then we can use it in just one place as well.
can you add a task according to [[Creating New Issues|dendron://dendron.handbook/area.team.sop.create-new-issue]] ? (you'll need to run Sync Workspace as well as sync you workspace repo separately to get the updated task config)
note that you won't be able to do the last step of exporting to airtable yet, just ping me when its done and i'll make sure its exported

[kevinslin]

heads up that this is another chore task since its not user facing :)

(if its not useful in a user facing changelog, it should be chore)

[eleweek]

@kevinslin Ah got it. Sorry for the misclassification.