fix: sdk render rate drop alert logs

[sakksham7]

Type of Change

• Bugfix
• New feature
• Enhancement
• Refactoring
• Dependency updates
• Documentation
• CI/CD

Description

#1519
This PR enhances the SDK logging mechanism to better track the lifecycle of SDK elements and improve observability:

1. Added new ORCA_ELEMENTS event - Logged when hyper.elements() is called to track when the elements instance is created
2. Fixed ORCA_ELEMENTS_CALLED event timing - Now correctly logged when element.mount() is called instead of at elements creation
3. Fixed APP_RENDERED event timing - Moved the render latency calculation to trigger when the element is actually mounted (via mountElement flag), providing more accurate load time metrics
4. Added cardCvc component support - Added cardCvc to otherElementsComponents array for proper component tracking
5. Added priority logging for ORCA_ELEMENTS - Ensures critical lifecycle events are always logged
   These changes provide better visibility into the SDK initialization flow and help distinguish between:

• SDK initialization (ORCA_ELEMENTS)
• Element mounting (ORCA_ELEMENTS_CALLED)
• App rendering completion (APP_RENDERED)

How did you test it?

Tested manually by:

• Loading the SDK and verifying the correct sequence of log events
• Verifying ORCA_ELEMENTS is logged on hyper.elements() call
• Verifying ORCA_ELEMENTS_CALLED is logged on element.mount() call
• Tested with cardCvc component to ensure proper inclusion

Screen.Recording.2026-04-28.at.4.09.48.PM.mov

Checklist

• I ran npm run re:build
• I reviewed submitted code
• I added unit tests for my changes where possible

[semanticdiff-com]

Review changes with