Application lifecycle management (ALM) for Power Automate and Power Apps is still evolving. Deployment between the environments using Solution packaging, environmental variables are available but only for CDS enabled environments.
Still after shipping from lower region (Dev) to upper region (Prod) using Solutions, the connections has to be reestablished before activation of Flows.
By default, when new flows are imported, they will be in a disabled state since connections still need to be established. Upon establishing connection(s) and saving the flow, the flow will become activated.
Reference
That being said, you may need to manually change the HTTP url to map the new Flow url after import. This is the only way today.
Coming from the Dynamics CRM (CDS) background, I know how the earlier version of Workflow & child workflow deployment deploys seamlessly, I will expect that to happen in the future.