enhance(publish): track templateVersion on initialization

[kevinslin]

enhance(publish): track templateVersion on initialization

Currently, dendron publish will always try to fetch the latest version of the template from git.
This isn't great as the latest version can have breaking changes.

This commit is the first in a series that adds versioning to the publishing templates to make upgrades and deployment less brittle.

• introduce templateVersion config variable that tracks version of template being published
• dendron publish init
  • no longer upgrades the template
  • writes templateVersion on initialization

The model we are moving to:

The NextJS Template is tightly couplped to deployments of the dendron mono repo.
Because it is not published to NPM but via github, versioning is maintained via git tags. 

Releases will be published under a git tag `v{VERSION}` where `VERSION` corresponds to the version of the dendron. 

Next:

• introduce dendron publish upgrade which
  • if tempalte is out of date, will upgrade and update templateVersion command
    • NOTE: because template version is tied to CLI version, we cannot update a template ahead of the CLI version
  • if template is newer then CLI, will prompt to upgrade the CLI
• clean up github actions template and tutorials to use dendron publish upgrade with tracked versions (vs deploying from the latest version)

[jonathanyeung]

What happens if config version exceeds engine Version? Shouldn't we do Math.min(configVersion?, engineVersion) ?

[kevinslin]

we don't want to do a min in this case because configVersion is source of truth. if the engineVersion is lower, we need to ask the user to update the engine because they've published using a higher version. i've done a writeup of this here, will also share as an async > https://docs.google.com/document/d/1dZ3X039TqQyUMaRYx9KJSFVpJMEHgtjRbqdAdFDGWX8/edit