RELATIONAL_JDBC: Move Events to dedicated Quarkus datasource

### Is your feature request related to a problem? Please describe.

Move Events to dedicated Quarkus datasource

### Describe the solution you'd like

Presently all the feature that talk to persistence use the same quarkus databasource, which means they share the same resources in terms of jdbc connection, for the seperation of concerns POV we should be able to give independent feature for example events to their own dedicated datasource to let the default source for normal polaris operation.

### Describe alternatives you've considered

_No response_

### Additional context

_No response_

The issue names no files, tests, or entry points. Start by locating the Events persistence path and the Quarkus datasource configuration, then determine the required isolation boundary. Done means Events use a dedicated datasource while normal Polaris operations remain on the default datasource.

Written by the indexing model from the issue text.