Fix cache-key test on release branches (#58546)

Summary:
Pull Request resolved: #58546

`getCacheKey` only hashes package contents when the package version ends in
`-main`; published releases short-circuit and return the version string. The
test asserted only the main-build property, so it could never pass on a release
branch, where two calls with different package contents both return the version.

The test now asserts the property that actually holds for each case: differing
keys on main builds, and the version string on published releases. This also
adds coverage for the published-release path, which previously had none.

Changelog: [Internal]

___

Differential Revision: D120209439

fbshipit-source-id: 9ebe74bad70ffca7bc7eb8b61fa8020b56219e8f

Author: fabriziocucci

packages/react-native-babel-preset/src/__tests__/cache-key-test.js

@@ -22,8 +22,19 @@ function getCacheKey(packageContents) {
   return require('../index').getCacheKey();
 }
 
-test('cache key includes package metadata for main builds', () => {
-  expect(getCacheKey('{"dependency":"1.0.0"}')).not.toBe(
-    getCacheKey('{"dependency":"2.0.0"}'),
-  );
-});
+const {version: packageVersion} = require('../../package.json');
+
+// Only `-main` versions hash package contents; published releases short-circuit
+// to the version string, so each build asserts a different property.
+if (packageVersion.endsWith('-main')) {
+  test('cache key includes package metadata for main builds', () => {
+    expect(getCacheKey('{"dependency":"1.0.0"}')).not.toBe(
+      getCacheKey('{"dependency":"2.0.0"}'),
+    );
+  });
+} else {
+  test('cache key is the package version for published releases', () => {
+    expect(getCacheKey('{"dependency":"1.0.0"}')).toBe(packageVersion);
+    expect(getCacheKey('{"dependency":"2.0.0"}')).toBe(packageVersion);
+  });
+}