feat(svc): add recording start method using event template name and type

[andrewazores]

• chore(svc): extract EventOptionsBuilder from Cryostat application
• chore(svc): add recording start method using event template name and type

Related to cryostatio/cryostat-agent#162
Related to https://github.com/cryostatio/cryostat/issues/1578

This extracts the EventOptionsBuilder from the Cryostat application into -core, then augments the JMC IFlightRecorderService by introducing a subinterface CryostatFlightRecorderService that allows for additional/higher-level operations, such as dynamically starting a recording using an event template name+type rather than the JMC IConstrainedMap. This will support starting recordings by network request by asking the Agent to simply use a .jfc file available to it locally, rather than needing to reserialize the settings defined by that .jfc and transmit that over the network, where those settings would be originally retrieved by querying the raw .jfc form from the Agent and parsing it to create the IConstrainedMap model.

A further enhancement to come later will be to allow supplying the entire XML (.jfc) Document on the recording creation request. The CryostatFlightRecorderService implementation will either convert this to the IConstrainedMap server-side, or pass it as-is to the Agent for conversion, so that the XML content of Custom event templates does not need to be reserialized between XML, POJO, and possibly JSON in several stages along the flow.

Some serialization-related classes are also extracted (and minor refactorings done) from the Cryostat application into -core here, since they will be useful for facilitating (de)serialization of these structures for communication between Cryostat and the Agent.

[maxcao13]

Makes sense to me, looks good!

[tthvo]

Looks good! I just have some small questions above.