Make Service Instance Meta Data Configurable (currently hard coded to 64).

#### Feature Description

Add configuration to increase number of meta data entries that can be associated with each service instance.
The current limit is hardened to 64.

#### Use Case(s)

As part of service instance registration, I need to associate meta data that is larger than the allocated space of 64 entries (512 bytes per entry) with each service instance.

The number of entries is approx 1000.
If this limit was configurable, this would solve the issue.

If this is not feasible, are there any other patterns available to achieve the same.

One option is to link to an entry (or entries) in the key value store to the service instance via a meta data entry, but this add complexity to the logic.
The writer can use transactions to add the service instance(s) and KV store entries in one atomic operation.
However, the reader uses a blocking query to get notified on changes to the service(s), but then would have to execute another read from the KV store. This introduces potential consistency issues, which should be possible to solve, but adds complexity to the logic.