Converting a HTTP Trigger into a Child Workflow in Power Automate Using a HTTP trigger requires Premium licence and with the Child Workflow in a solution alleviates the need of premium license.
Other advantages using a solution:
Application Lifecycle Management: Facilitates deployment. Child Workflow: Allows for a more modular and manageable flow structure. Easier Ownership Management: Simplifies updates to the flow owner. I recreated the child workflow within the solution selecting the Manually trigger a flow trigger and updated the parent flow to use the flow as child workflow.