Test if action, trigger or rule already exists before deployment

Can we in unit/integration tests have a convention some functional code that between tests cases being run (or by default at the top of each unit test) for namespace conflicts? That is, can we look at the test about to be run,

For example, I see us leveraging the all the YAML files in each unit test (and move away from hardcoded strings) where we have a standard function that
- parses the manifest YAML
- creates a std. structure containing information about the YAML file including:
- number of actions in YAML
- number of parameters in each Action (both input and output)
- assures that each Package/Action/Trigger/Rule name within the YAML is unique (no intra-file cut/paste errors)
- is able to (maybe not by default) iterate over the action, trigger and rule names and is able to WARN if the names already exist in the namespace.

Of course, we would want to leverage the code to test if action/trigger/rule already exists for the command line to allow user to see where they are/will overwrite existing code.

Start by reviewing the unit and integration tests and the YAML manifests they use, then trace how deployment and command-line handling currently process action, trigger, and rule names. Done should include a defined convention for detecting intra-file duplicates and warning about namespace conflicts in tests and the command line.

Written by the indexing model from the issue text.