ci: expose python version for translate tests

[romanc]

Description

With NDSL supporting more than one version of python, we'd like to have the possibility to run pyFV3 translate tests with different versions of python. This PR adds an optional input variable to the workflow_call which allows calling workflows to specify the python version.

The PR also removes usage of the component_trigger input variable. The input is redundant with component_name, which is a non-empty string whenever component_trigger is true. I keep the input around until we update all calling workflows to not set it anymore.

How Has This Been Tested?

By running the current CI. The workflow_call was tested with NOAA-GFDL/NDSL#376 requesting to run PyFV3 tests with python 3.12 and with the default python version.

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: N/A
• 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: N/A
• Targeted model if this changed was triggered by a model need/shortcoming: N/A