fix hermes param handling in test-e2e-local.js (#48068)

[vonovak]

Summary:
this is the same as #48068 but for the 77-stable branch. I realized now that the standard procedure is to use a pick request (but the change is pretty trivial), let me know if I should do that instead.

why: running yarn test-e2e-local -t "RNTestProject" -p "Android" -h false -c $GITHUB_TOKEN would actually build the app with Hermes even though it's specified as disabled.

This is because of the if (argv.hermes == null) condition whose body would not execute. The condition was changed recently.

Reason for await being used:

Error ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈ scripts/release-testing/test-e2e-local.js:303:32

Cannot get argv.hermes because property hermes is missing in Promise [1]. [prop-missing]

     scripts/release-testing/test-e2e-local.js
     300│     'reactNativeArchitectures=arm64-v8a',
     301│     'android/gradle.properties',
     302│   );
     303│   const hermesEnabled = (argv).hermes === true;
     304│
     305│   // Update gradle properties to set Hermes as false
     306│   if (!hermesEnabled) {

     flow-typed/npm/yargs_v17.x.x.js
 [1]  80│     argv: Argv | Promise<Argv>;

Changelog:

[INTERNAL] [FIXED] - fix hermes param handling in test-e2e-local.js

Pull Request resolved: #48068

Test Plan: tested locally

[react-native-bot]

	Warnings
⚠️	📋 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.
⚠️	📋 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.

Generated by 🚫 dangerJS against 0d3f8c1

[cipolleschi]

Code looks good to me.
Please, open a pick request anyway, otherwise we will forget about this PR.