fix(metro-config): fix and realign the situation for metro config for 0.72

[kelset]

Summary:

As noted by @hoxyq here there's some inconsistencies with what happened with metro config and its releases.

Basically, it looks like 0.72.1 of metro-config was released from main branch instead of 0.72-stable, which means that currently 0.72 is in an inconsistent state for its package.

Relevant commits:

• for 0.72-stable 9ffe82e
• for main c5a47ab#diff-cbcd5b7d5c2dff9dbd901bc385916ed457d12cfcdf9c2ed16bb44d18bb49232f

It shouldn't be too big of a deal, and this PR should realign the situation so that the metro-config folder in 0.72-stable is exactly the same as main (and future 0.72.x releases of metro-config will need to happen from this branch, while main is on 0.73.x now).

Because I'm doing it this way, CI won't trigger and won't attempt to re-release 0.72.1 of metro-config.

Changelog:

[INTERNAL] [FIXED] - fix and realign the situation for metro config for 0.72

Test Plan:

N/A

[github-actions]

	Warnings
⚠️	🔒 package.json - Changes were made to package.json. This will require a manual import by a Facebook employee.

Generated by 🚫 dangerJS against 27f9096

[huntie]

Thanks for catching the detail about the incremented version. Would've read from npm but not from the local monorepo copy 👍. Only the template needs the new API from ^0.72.1.