Allow configuration of the broker in local environments

[josephmckinsey]

Creates a new HELICSFederateConfig which people are intended to subclass from.

• It has a "apply_to_federate_info" function that lets you set the properties on the FederateInfo HELICS object to use the correct broker, etc.
• It should be compatible with helics.helicsFederateInfoLoadFromString when you specify the static_inputs.json file path (although this does not set all the required properties most federates need like period information).
• It only contains name, broker, and communication information and not timing information.
• There is a .from_multicontainer class which lets you combine params with the existing multicontainer BrokerConfig (which has slightly different names.

The WiringDiagram now supports setting the broker information in shared_helics_config or in components under helics_config_override as a SharedFederateConfig class which includes only the broker information and no names.

The multicontainer does not support setting the broker information with an override right now, since the configurations are slightly different. We may be able to deprecate the multicontainer BrokerConfig at a later date.

[josephmckinsey]

I just realized that we don't pass the broker configuration to the broker when we make the run script. Will fix tomorrow.