The ConditionalOnProperty annotation requires kebab-case in its
attributes in order to correctly match them using relaxed binding to
spring loaded properties. In other words, to match to both my-example
and myExample, the @ConditionalOnProperty must refer to my-example. If
it refers to myExample, then it only works explicitly on myExample and
relaxed binding to my-example doesn't work.

To avoid this, we add an ArchUnit test that verifies that none of the
attributes of ConditionalOnProperty use camelCase. It does this simply
by checking for capitalized letters. If it fails, the error message
includes all the needed details, like the location of the forbidden
annotation, the specific attribute, and the failure.

To overcome the problem, simply switch to using kebab-case in the
attributes of ConditionalOnProperty.

ConditionalOnProperty requires specifying names of properties using
kebab-case.

This ensures that camunda.tasklist.webapp-enabled can be used rather
than requiring camunda.tasklist.webappEnabled explicitly.

Note that the docs document it as camunda.tasklist.webappEnabled, but
this change is backward compatible, as camunda.tasklist.webappEnabled
can still be matched due to relaxed binding. We decided to use
kebab-case for configs in the docs, but they have not been adjusted yet.

ConditionalOnProperty requires specifying names of properties using
kebab-case.

This ensures that camunda.operate.webapp-enabled can be used rather
than requiring camunda.operate.webappEnabled explicitly.

Note that the docs document it as camunda.operate.webappEnabled, but
this change is backward compatible, as camunda.operate.webappEnabled
can still be matched due to relaxed binding. We decided to use
kebab-case for configs in the docs, but they have not been adjusted yet.

ConditionalOnProperty requires specifying names of properties using
kebab-case.

This ensures that camunda.tasklist.importer-enabled can be used rather
than requiring camunda.tasklist.importerEnabled explicitly.

Note that the docs document it as camunda.tasklist.importerEnabled, but
this change is backward compatible, as camunda.tasklist.importerEnabled
can still be matched due to relaxed binding. We decided to use
kebab-case for configs in the docs, but they have not been adjusted yet.

ConditionalOnProperty requires specifying names of properties using
kebab-case.

This ensures that camunda.operate.importer-enabled can be used rather
than requiring camunda.operate.importerEnabled explicitly.

Note that the docs document it as camunda.operate.importerEnabled, but
this change is backward compatible, as camunda.operate.importerEnabled
can still be matched due to relaxed binding. We decided to use
kebab-case for configs in the docs, but they have not been adjusted yet.

ConditionalOnProperty requires specifying names of properties using
kebab-case.

This ensures that camunda.tasklist.feature-flag.process-public-endpoints
can be used rather than requiring
camunda.tasklist.featureFlag.processPublicEndpoints explicitly.

This change moves the RequireKebabCaseInConditionalOnPropertyArchTest to
the io.camunda package as it covers all those classes.

This makes it easier for other ArchTests to also align to the structure
of the codebase that they work with. The end goal is a module that
organizes its test in way where it's easy to see at a glance what code
is covered by these tests.