refactor/remove-org.reflections.reflections-dependency

[codespearhead]

• Utilized JPA's Metamodel API to retrieve all managed entity classes.
• Prefixed instance variables and methods with this. to enhance code clarity.

[appiepollo14]

In general a great PR. I've added a few comments. Please see this link for more references. I believe for now this is a sufficient solution for truncating all tables, however, I still have my doubts whether the DatabaseIntegrationTest is designed as it should.

Another directions would be:

• Truncate all tables from schema X via a native SQL statement.
• Rewrite the tests to allow order in the tests so no clearing in between tests has to happen.

[codespearhead]

If the primary goal of that class is to roll back the database after each test, you can use the io.quarkus.test.TestTransaction annotation instead [1].

Ideally, this annotation should be applied to tests that modify the database. However, I applied it to entire classes, leaving the method-level annotation as a future optimization, since most of the methods change the database anyway.

The issue I'm facing now is that some tests share a state instead of being able to run independently (see "TODO" in ArticlesResourceIntegrationTest.java).

Conversely, the org.junit.jupiter.api.Order annotation can be used to have the tests run in a predictable order. However, it's best not to overuse it so the tests can run in parallel.

---

[1] https://quarkus.io/guides/getting-started-testing#tests-and-transactions
[2] org.junit.jupiter.api.Order