Fix npm latest tag issue when releasing patches

[lunaleaps]

Summary:
Changelog: [Internal] Fix npm latest tag issue that occurs when we release a patch on an older minor version

Context:

• There are two types of tags, git and npm, they are unrelated.

• When we publish a stable release, we set the git tag latest. This logic is faulty when we release a patch to an older version.

• When publishing a package to npm, if you don't provide an explicit tag, the latest tag will be applied -- at least that's how I've understood the docs here. This again is faulty logic when we release a patch to an older version.

• npm and git's latest tag should always point to our most recent stable version

This change:

• Introduces a --latest flag for bump-oss-script that will indicate that the release we're running (either a stable or pre-release) should really be considered "latest"
• If the version is not a pre-release and the --latest flag is set, we will set the git latest tag
• Later, in the circleCI job that we use to publish the npm package, we will see if the current commit is git-tagged as latest. If it is, then we'll explicitly tell npm to use latest tag but most importantly, if it's not, we'll set a tag of the form {major}.{minor}-stable.
• This type of tag (ex. 0.66-stable) is new and the intention is that it will always point to latest of that minor version.

Differential Revision: D32196239

[facebook-github-bot]

This pull request was exported from Phabricator. Differential Revision: D32196239

[pull-bot]

	Messages
📖	📋 Missing Changelog - Can you add a Changelog? To do so, add a "## Changelog" section to your PR description. A changelog entry has the following format: [CATEGORY] [TYPE] - Message. Details CATEGORY may be: General iOS Android JavaScript Internal (for changes that do not need to be called out in the release notes) TYPE may be: Added, for new features. Changed, for changes in existing functionality. Deprecated, for soon-to-be removed features. Removed, for now removed features. Fixed, for any bug fixes. Security, in case of vulnerabilities. MESSAGE may answer "what and why" on a feature level. Use this to briefly tell React Native users about notable changes.
📖	📋 Missing Test Plan - Can you add a Test Plan? To do so, add a "## Test Plan" section to your PR description. A Test Plan lets us know how these changes were tested.
📖	📋 Missing Summary - Can you add a Summary? To do so, add a "## Summary" section to your PR description. This is a good place to explain the motivation for making this change.

Generated by 🚫 dangerJS against 95ebb0d

[analysis-bot]

Platform	Engine	Arch	Size (bytes)	Diff
ios	-	universal	n/a	--

Base commit: 88ebec9
Branch: main

[analysis-bot]

Platform	Engine	Arch	Size (bytes)	Diff
android	hermes	arm64-v8a	9,350,969	+0
android	hermes	armeabi-v7a	8,333,034	+0
android	hermes	x86	9,983,357	+0
android	hermes	x86_64	9,768,730	+0
android	jsc	arm64-v8a	10,665,547	+0
android	jsc	armeabi-v7a	9,311,086	+0
android	jsc	x86	10,777,605	+0
android	jsc	x86_64	11,216,905	+0

Base commit: 88ebec9
Branch: main

[kelset]

Looks great!

The only piece of feedback I think it's relevant is that this is going to land on main, but we might want to cherry pick in the branches too (from 0.67 down to 0.64 or even 0.63/0.62 tbh) so that if someone was to do a new patch release for those it would have this corrected logic in place. (and we wouldn't need to rely on them to remember to cherry pick 😅)

[facebook-github-bot]

This pull request has been merged in 68e6788.