Rename quarkus.hibernate-search-orm.enabled to quarkus.hibernate-search-orm.active and repurpose quarkus.hibernate-search-orm.enabled to disable Hibernate Search at build time

[yrodiere]

The motivation is two-fold:

• I've been made aware that other extensions use .enabled to enable/disable an extension at build time, but Hibernate Search was using it to disable the extension at runtime. This PR restores consistency
• We still need something to disable Hibernate Search at runtime, because that's what was requested in the original use case. .active solves that.

I'm not very enthusiastic about the name of the property quarkus.hibernate-search-orm.started, but that's the best I could come up with. I'm open to suggestions, keeping in mind that quarkus.hibernate-search-orm.enabled is not an option since it has a different purpose. => Renamed to .active, a bit better.

This is related to a conversation we had on the Quarkus mailing list: https://groups.google.com/g/quarkus-dev/c/rfWe_jrSzJY/m/u5282G-SEAAJ?utm_medium=email&utm_source=footer

For context, the conversation branched from there: https://groups.google.com/g/quarkus-dev/c/o8gtDJoV7VY/m/R9ub7DPqAgAJ?utm_medium=email&utm_source=footer

For the migration guide:

## `quarkus.hibernate-search-orm.enabled` was renamed to `quarkus.hibernate-search-orm.active`

If you were previously using the configuration property `quarkus.hibernate-search-orm.enabled` to enable/disable Hibernate Search at runtime (by setting the config in deployment configuration files, environment variables or commandline parameters), then you should use the configuration property `quarkus.hibernate-search-orm.active` instead.

`quarkus.hibernate-search-orm.enabled` is now aligned with Quarkus conventions and disables the extension at *build time*, which cannot be reverted at runtime.

Creating as draft because this PR is based on #26838 , which should be merged first.

[Sanne]

+1 to restore consistency with other extensions - and it's nice to have the ability to disble it at build time.

Like you, I'm also not very happy with the .started suggestion. .active could fit better?

[yrodiere]

Like you, I'm also not very happy with the .started suggestion. .active could fit better?

It's confusingly close to enabled in my opinion, but it's probably a bit better than started indeed. I'll wait for others to chime in and will rewrite everything accordingly :)

@gsmet, any opinion?

[yrodiere]

Renamed .started to .active. Unless someone has a better idea, that's the name we'll keep, and that's what I'll use when implementing the same for Hibernate ORM / Envers.