[react] Remove .0 for releaseCycle 19

[BiNZGi]

We only track major versions as releaseCycles

From discussion in #6680

[captn3m0]

NB: This will have to be split again once 19.1 releases, since 19.0 and 19.1 are considered supported in parallel.

[usta]

@BiNZGi @captn3m0 in this case lets make them .X format so it will fix all upcoming problems.
( I mean 15 -> 15.X , 16-> 16.X .... 19 -> 19.X )

[usta]

sure this wont work if they make 19 and 19.1 alive(supported ) in same time

[BiNZGi]

19.0 and 19.1 are considered supported in parallel.

I am not sure about this. Looking at https://react.dev/versions I cannot find a minor or patch release that is released later than the next major. I would assume that only the latest version per major version is supported.

https://react.dev/community/versioning-policy#all-release-channels

Both Latest and Canary channels are officially supported for user-facing applications

https://react.dev/community/versioning-policy#latest-channel

Latest is the channel used for stable React releases. It corresponds to the latest tag on npm.

There can be only one latest tag on npm, see https://www.npmjs.com/package/react?activeTab=versions. When 19.1.0 will be tagged as latest 19.0.x will no longer be supported. Next latest after 19.1.0 will be 19.1.1, 19.2.0 or 20.0.0.

.X format

@usta The cycles would be as follow: 19.1, 19.0, 19.x, 18.x, 17.x, ...