Improve handing of "pattern" fields during object creation

[jeremystretch]

Proposed Changes

Improve the handling of fields which return a set of multiple values derived from a given pattern, i.e. ExpandableNameField and ExpandableIPAddressField. These are currently handled explicitly as an anti-pattern e.g. under ComponentCreateView.

I still need to do some research to determine our options, but I wanted to get this initiative documented.

Justification

The way these "expanded" fields are handled currently requires intervention within the view logic, and does not scale well to include additional implementations, such as the expansion of module bay positions under #7844.

[jeremystretch]

I ended up refactoring most of the device component creation logic under #7846. This is no longer needed.