[FEATURE] xname assignment for discovery

[njones-lanl]

Is your feature request related to a problem? Please describe.
xnames are currently assigned very statically, and it doesn't work for the format that xnames try to assign (cabinet slot etc)

Describe the solution you'd like
To me this seems like something we'd either need to have key off something set in redfish, or off of some sort of human input.

Describe alternatives you've considered
Can't think of any.

Additional context
Currently all nodes populate with a prefix of x1000c1s7.

[davidallendj]

This was something that me and @synackd talked about before and I think the solution to this may be related to #2 by allowing the user to specify other parameters. I'm stilling thinking about the best way to specify each node name and when. I'll probably end up adding another column to the cache database and allow changing the name right after a scan and/or when running a collect.

[alexlovelltroy]

I toyed with this for a while and didn't find anything I liked. Here's what I explored:

1. create a yaml configuration file or obtain one from the vendor that describes a normal rack with some level of detail which allows the system to infer location in the rack through switch-port number for the BMC. Only require manual intervention in cases where the rack is not "normal"

2. Use PDU controls to switch on each host and identify it based on what switch port ultimately lights up.

3. Bring up nodes without location information and use another process to update xnames after boot.