Add mappings versions to ClusterState.Builder convenience methods

[williamrandolph]

This is a follow-up to #99307, adjusting convenience methods that used to take TransportVersion arguments to account for MappingsVersion maps.

[elasticsearchmachine]

Pinging @elastic/es-core-infra (Team:Core/Infra)

[ldematte]

LGTM with one comment

[ldematte]

Minor: it seems to me that this method is always called with an empty map. Maybe we could remove the parameter and give it a clearer name, like putCompatibilityVersionsWithNoSystemIndexMapping (I know, it's long, maybe there is something better). But something that makes the caller aware they are skipping something.

[williamrandolph]

The API I'm aiming for here is:

1. a method that puts a CompatibilityVersions object to the map, keyed to node ID
2. a method that sets the entire map of CompatibilityVersions for the builder
3. a convenience method that takes all the kinds of versions and constructs a CompatibilityVersions object. As we add new kinds of versions, we'll add arguments to this method.

Since "CompatibilityVersions" is already plural, it's a little awkward to name the method that takes the whole map. I think "nodeIdToCompatibityVersionsMap" might be a more informative name.

But I think I want to keep the three-arg compatibility versions method as-is. Eventually we'll add more things to CompatibilityVersions, and I don't want to add methods to handle subsets of available types of versions.

[thecoop]

Is there a name a bit more descriptive we could use?

[williamrandolph]

How about nodeIdsToCompatibilityVersions?

[thecoop]

Works for me!

[williamrandolph]

@elasticsearchmachine please run elasticsearch-ci/part-1