chore(alerts): remove the package-info files added by the alerting regroup

[manerow]

What this pull request does

The alerting regroup (PR #35032) added a package-info.java to each of the 23 packages under alerting and events.consumer, and to apps.bundles.insights.template. Each holds one Javadoc sentence and nothing else: no annotations, no imports. Nothing reads them (no test, Checkstyle rule or build step), and no other package in openmetadata-service has one, so they only made these packages look different from the rest. This removes all 24.

The rules they described stay where they are enforced: AlertingArchitectureTest fails the build when a package crosses its boundary, and the decision record in docs/decisions/ explains how an alert names its consumer.

How it was tested

A clean build of openmetadata-service with its dependencies, and AlertingArchitectureTest, ConsumersTest and EventSubscriptionMapperTest (14 tests), pass. Javadoc runs with doclint off in every module, so no build step needs package docs.

Fixes #35030

[gitar-bot]

Code Review ✅ Approved

🟢 Low risk · Removing 24 package-info files deletes only package Javadocs, leaving executable code and alerting behavior unchanged.

Removes the 24 one-sentence package-info.java files added by the alerting regroup from alerting, events.consumer and apps.bundles.insights.template. Nothing reads them, and the boundary rules remain enforced by AlertingArchitectureTest. No issues found.

Verification

Rules No rules evaluated

Functional validation Not enabled

Set up

Auto-approval Not enabled

Set up

_{For more verification details, comment gitar display:verbose.}

Options

Display: compact → Showing compact verification results.

Comment with these commands to change the behavior for this request:

Compact

gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Powered by Gitar — free for open source}