Rollback TIG use case senarios functionality introduced in v0.15.0

[chowsanthony]

Based on feedback from eSub participants, the TIG team decided during an internal meeting to roll back the TIG use case scenarios functionality introduced in v0.15.0. The team plans to, in the next grant extension, engage CTP to seek clarity on the Agency’s eCTD plans.

[SFJohnson24]

this will need to be rolled back in engine as well as the new open rules repo: remove the USE_CASE from the .env as well as the from the templates from the git action.

from engine-- we will go back to the hardcoded template and remove the -uc command line argument as well as the report use case

[SFJohnson24]

with the rollback--we will no longer have a way to handle custom domains for TIG (assuming TIG wants to supports custom domains). The command line use-case argument gave a way to tell engine that all the domains submitted for a validation were of a specific use case and thus defined the use case of custom domains submitted for validation. With this removal, custom domains will error when interacting with library and will also likely fail to execute for a majority of rules as there is no logic to delineate what use case they are for rule scoping and execution.

#1556

[SFJohnson24]

TIG0514 will need to be looked at with the rework as this was the ticket that sparked the -use_case parameter

[SFJohnson24]

per discussion today: use-case command line argument will be used only for custom domain ID; roll back former hardcoded standard domain definition files; this will hopefully be moved to standard metadata in later TIG versions