Bump Hermes to 0.7.2 for v0.64

[Huxpro]

Summary

https://github.com/facebook/hermes/releases/tag/v0.7.2 is out so we can bump the pod version 🎉

Question:
Is ~> 0.7.2 too strict? Would >= 0.7.2 be better?
Also, It doesn't look like we are restricting any version on the trunk?

Changelog

[INTERNAL] - Bump Hermes version

Test Plan

Quoting from facebook/hermes#373

I can verify 0.7.2 is working with USE_HERMES=1 bundle exec pod install --repo-update 🎉

[alloy]

Is ~> 0.7.2 too strict? Would >= 0.7.2 be better?

I think keeping it is good, e.g. the JSI ABI differences thus far have meant that RN versions can't just take in any Hermes version, so locking it to patch versions equal to or higher than 0.7.2 seems good 👍

Also, It doesn't look like we are restricting any version on the trunk?

Can you elaborate on what you’re referring to by this?

[Huxpro]

@alloy I just have another look at https://guides.cocoapods.org/using/the-podfile.html and realize everything was good :)

so locking it to patch versions equal to or higher than 0.7.2 seems good

I misunderstood ~> 0.7.2, which actually means it only take patch releases but not minor. Yeah that is what we want.

Also, It doesn't look like we are restricting any version on the trunk?
Can you elaborate on what you’re referring to by this?

Yeah I mean we did not specify a version at the master branch, which actually means it will always take the latest, which is also what we want ;)

[grabbou]

Just curious if this was intentional or a mistake that this PR was opened against release branch and didn't land on master? In such case, it may need to be synced once again.

[Huxpro]

@grabbou it was intentional since I observed that they are already not synced: we specified 0.7.1 at the 0.64 branch but did not specify a version at the master branch.

But quoting my later realization:

Yeah I mean we did not specify a version at the master branch, which actually means it will always take the latest

which seems to be what we want?