Configurable dynamic port range

[prestonp]

The intent of this change is to support shifting the range used for assigning dynamic ports (#8186).

This makes the static dynamic port range configurable per new client settings dynamic_port_range_min and dynamic_port_range_max.

[tgross]

Hi @prestonp! Thanks for submitting this PR!

This probably works ok for a single-node cluster that's both a server and client, but it looks like it'll break down in a production environment with multiple nodes.

You have the dynamic port range is configured on a per-client basis, which definitely is the right thing to do because different clients will have different non-Nomad-managed services. But then the server doesn't have any way of handling that information on a per-client basis for scheduling purposes; there's only the global in structs/network.go. So when AssignPorts gets called by the scheduler, it'll always get the same answer.

The dynamic port range needs to be added to the Node struct so that it can be passed up from the client to the server with the fingerprint in node_updater.go.

[jrasell]

This functionality was added within #11167 and will be released in Nomad 1.2.0.

[github-actions]

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.