(RFE) Discuss setting pre-determined boot order ahead of assignment provisioning

[sadsfae]

This is an RFE/stub to discuss the viability of adding an additional argparse to quads-cli --define-cloud like --foreman or --boot-order foreman

e.g.

quads-cli --define-cloud cloud02 --boot-order foreman

This would achieve the following:

• If passed to quads-cli --define-cloud when the assignment becomes active it will supplant the default behavior of enforcing the equivalent of badfish -t director around here: https://github.com/redhat-performance/quads/blob/master/quads/tools/move_and_rebuild_hosts.py#L193 to instead enforce the -t foreman boot order.

• Additionally, we can field for this in our request forms for new assignments with the default to still enforce director-style boot order.

Pros

• If specified ahead of time folks who want to reprovision don't need to use badfish to perform one time boot or any of the other one-time boot/PXE operations we support. This might save some amount of time for tenants.

• If tenants want to reprovision often during their assignment this would save substantial time as there is no need to process temporal or permanent boot order re-arrangement.

• Yet to be seen or unknown, future requirements might be able to leverage this.

Cons

• It's hard to determine behavior of future assignments and sometimes they may pivot so this might not be all that useful
• We've really not seen a need or demand for this but it doesn't mean it won't be helpful.