Add missing @Override annotations flagged by CodeQL

[vharseko]

Closes the remaining ~1327 java/missing-override-annotation CodeQL alerts — the last large note-severity category from the ongoing CodeQL cleanup series (#122, #123, #126, #128, #130–#134).

Change

Every location CodeQL's java/missing-override-annotation flagged gets an @Override line inserted immediately above the method signature, at the same indentation, at the exact line the alert points to. 226 files, purely additive — 1327 @Override insertions plus the CDDL "Portions Copyright" header line on files that did not already carry one (220 via the standard header pattern, 6 with non-standard or missing headers handled individually).

No other code changes: no renames, no logic touched, no reordering.

Verification

@Override is compiler-checked — javac fails hard when it is placed on a method that does not actually override or implement anything from a supertype ("method does not override a method from its superclass"). Rather than review 1327 insertions by hand, the real proof is a clean build: the entire reactor was built from the root pom.xml (mvn install, all 28 modules) after the insertions, with no manual fixes needed afterward.

Result: BUILD SUCCESS, all 28 modules, 1442 tests, 0 failures, 0 errors (164 skipped, same skips as on master) — including connector-framework-internal (469 tests) and ldap-connector with its embedded OpenDJ (159 tests). Also spot-checked ~30 random insertions by hand across different files and annotation styles (interface method declarations, anonymous inner classes, nested static classes) before the build, all correctly placed.

Note for merge order

This branch is cut from origin/master like the other open CodeQL PRs in the series and was not rebased against any of them. Several files here are also touched by #126, #128, #131, #132, and #133 (e.g. AesGcmEncryptor, WebSocketConnectionGroup, CSVFileConnector), so merging this one will need a rebase of whichever of those merge after it — nothing here should conflict semantically (this PR only ever adds an @Override line, never touches the same line another PR modifies), but the merge order across the series is a judgment call, not mine to make unilaterally.