At the root of this, the main problem is that if you create a new flow version through the SFDC flow editor interface, the flow will have a new version of the flow translations based on the previous translations.

But if you DEPLOY a flow, the new flow version is created WITHOUT flow translations at all.

This would be fine, if gearset would allow us to reliably deploy the flow WITH flow translations, even if the flow translations had "no changes". (Gearset does not allow us to deploy items with no change, and sometimes doesn't even show them in the comparison--as is the case with flow translations)

Currently, if I make a change to a flow that does NOT impact the flow translation, I have to:
1. Deploy the flow, which creates a new version of the flow in the target environment, but WITHOUT any translations.
2. recompare, and then find the flow translation (which is now "new" or "different") because the target environment doesn't have translations for the flow, and deploy the flow translation

Just allow me to force-deploy flow translations (and always show flow translations, even if they are not different), and it would save me a lot of time