The registering of Service Messages and Descriptors is not part of the instantiate.vi using dynamic dispatching

[Arrowin-87]

Proto files could have multiple services defined or multiple proto files each have a single service which results in multiple classes to be created by the (server) code generator. Although the registering of the messages and descriptors (server code) is only a single VI for all service classes it generates, it would be easier if the registering is part of a dynamic dispatch VI, one for each service class. The same principle is already implemented for the "Register gRPC Methods.vi"! Why not do this for the messages (data structures) and descriptors?
This will make the code easier to port to applications since both VI's (listed below by name) should be used as a (protected) SubVI within the instantiate.vi (which is actually already a dynamic dispatch VI) within the ServiceBase.lvclass. The user only has to use the Instantiate.vi from the API.

1st step:

• Register gRPC Messages.vi
• Register Descriptors.vi
  Both VI's to be placed under the Server API within the ServiceBase class as dynamic dispatch and to e overridden by the code generator.

2nd step:
Both VI's also to be added within Instantiate.vi

AB#2991658