build: specify built-in Talk version in package.json

[ShGKme]

☑️ Resolves

Allows to:

• Have the built-in Talk version in the repository history
• Have a PR to explicitly bump the built-in Talk version
• Reproduce a release package with a simple git checkout version + release:package instead of searching in the changelog for the Talk version
• Build release on CI. Before, a Talk version was manually specified by a developer during the release

Currently, it only affects the release:package script used in the releases.

Follow-ups:

• Use it for repo init instead of git clone spreed
• Automate built-in Talk version bump

[Antreesy]

LGTM, if you're fine with talk.stable naming in package.json

[ShGKme]

if you're fine with talk.stable naming in package.json

Any preferences? :)

[Antreesy]

Any preferences? :)

builtInVersion or coreAppVersion maybe?

[ShGKme]

Rebased to resolve conflict

[nickvergessen]

builtInVersion or coreAppVersion maybe?

Or branch or ...

But yeah stable sounds weird, especially when it's unstable while we build with 21.0.0-betas in the future and things a like?

[ShGKme]

Or branch

But 20.0.1 is not a branch...

when it's unstable while we build with 21.0.0-betas

Then it is in beta/rc instead of stable

[ShGKme]

Rebased onto main. Keeping the current simple name. It's simple to change it without any breaking changes.