ci: prepare for using a merge queue in PyFV3

[romanc]

Description

Using merge queues was talked about in the pace meeting in August. No concerns were raised and we've successfully adopted merge queues in NDSL with NOAA-GFDL/NDSL#194.

This PR configures PyFV3 tests to not only run on pull requests, but also in the merge queue (and when merging back into main - just for good measure). @fmalatino would you help me again as repo admin to do the repo configuration? Should be one-to-one from what we did in NDSL.

How Has This Been Tested?

Similar to what we have configured in NDSL. The new behavior will be apparent once we merge. I'll keep an eye out of oddities for the first couple PRs that get merged with the merge queue.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation: N/A
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules: N/A
• New check tests, if applicable, are included
• Targeted model if this changed was triggered by a model need/shortcoming: N/A