docs(events): document and deprecate objectId in favor of objectIdStr (AUD-907)

[vitoraykov]

Summary

Documents the objectIdStr property on the Event interface and marks the older numeric objectId property as deprecated. The objectIdStr property itself was added to the SDK in #177; this PR adds the user-facing documentation and the deprecation marker.

objectIdStr holds the affected object's identifier as a string and supports both numeric and non-numeric identifiers. The existing numeric objectId property is deprecated (kept for backward compatibility) — it contains -1 when the identifier is non-numeric, in which case the real value is only available in objectIdStr. New code should read objectIdStr.

Changes

• ADVANCED.md — add an explanatory paragraph plus a before/after code sample to the Event Reporting section showing event.objectIdStr (preferred) vs. event.objectId (deprecated).
• lib/events/types.ts — add a JSDoc @deprecated tag to the objectId property in the Event interface pointing to objectIdStr.
• CHANGELOG.md — add a Deprecated entry under Unreleased.

Notes for reviewers

• This is a soft deprecation. The JSDoc states that objectId is not scheduled for removal — matching the API changelog (Jun-08-2026). The @deprecated tag surfaces as an IDE strikethrough; it has no runtime effect. Please flag if you'd prefer stronger or weaker language.
• The generated dist/lib/events/types.d.ts is not edited here — it regenerates from source on build/release.
• Part of AUD-907. Parallel PRs apply the equivalent documentation + deprecation to the Python, Java, and C# SDKs, and a cross-language migration guide is going into api-docs.

Related

• Jira: AUD-907
• Code PR: feat(events): add objectIdStr field to Event interface #177 (added the objectIdStr field, AUD-903)