chore: remove ROKT_KIT_ATTACHED info log

[mattbodle]

Summary

• Remove the informational log emitted from RoktManager.attachKit() ("RoktManager: Kit attached, Rokt is ready") when the Rokt kit connects.
• Remove the now-unused ROKT_KIT_ATTACHED entry from the ErrorCodes map in src/reporting/types.ts.

Test plan

• eslint src/ — no issues
• tsc -p . --noEmit — no errors
• Jest suites roktManager, reportingLogger, logging-integration — 130 passed, 0 failed
• CI green

[cursor]

PR Summary

Low Risk
Observability-only cleanup with no changes to Rokt initialization, queuing, or ready callbacks.

Overview
Removes the informational reporting log that fired when the Rokt web kit connects in RoktManager.attachKit() ("RoktManager: Kit attached, Rokt is ready"). Kit attach behavior is unchanged: account/integration metadata is still stored, the message queue is still drained, and onReadyCallback still runs.

Deletes the unused ROKT_KIT_ATTACHED value from the shared ErrorCodes map in src/reporting/types.ts so reporting codes stay aligned with what the SDK actually emits.

^{Reviewed by Cursor Bugbot for commit c80c2e8. Bugbot is set up for automated code reviews on this repo. Configure here.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud