Reduce dependence on extensions backed by Spring

We should work towards having vert.x/netty/... alternative components in Camel and using those instead of the ones that rely on Spring.

Why: our Spring hacks are hard to maintain.

- [ ] Springless ActiveMQ extension
- [ ] Springless Hashicorp Vault extension
- [x] Springless JDBC extension
- [x] Springless Jira extension
- [x] Springless JPA extension
- [ ] Springless JMS extension
- [ ] Springless SQL extension
- [ ] Vert.x RabbitMQ extension

Review the unchecked Springless ActiveMQ, Hashicorp Vault, JMS, SQL, and Vert.x RabbitMQ items, along with the completed JDBC, Jira, and JPA items. First determine the intended alternative component for each remaining extension and how the existing Spring-backed extensions are organized. Done would mean the remaining checklist items have suitable non-Spring implementations in Camel Quarkus.

Written by the indexing model from the issue text.