To get a hub-specific schema, the hubverse transform will need to know that top-level location of the hub (so it can find hub-config. To make getting that information more straightforward, we'll now instantiate ModelOutputHandler with 3 parameters instead of 2 (splitting the high-level hub location from the remainder of the incoming model-output path).
This PR is a re-factor that lays the groundwork for addressing this issue: https://github.com/hubverse-org/hubverse-transform/issues/14
To get a hub-specific schema, the hubverse transform will need to know that top-level location of the hub (so it can find
hub-config. To make getting that information more straightforward, we'll now instantiateModelOutputHandlerwith 3 parameters instead of 2 (splitting the high-level hub location from the remainder of the incoming model-output path).