Fix #5250 : Add support for logging device DPI events

[Tejas-67]

Explanation

Fix #5250 In the EventBundleCreator class, introduced a new item in the bundle to log the screen density of the device. Stored using the key "screen_density" and value retrieved from resources.displayMetrics.screenDensity .

Essential Checklist

• The PR title and explanation each start with "Fix #bugnum: " (If this PR fixes part of an issue, prefix the title with "Fix part of #bugnum: ...".)
• Any changes to scripts/assets files have their rationale included in the PR explanation.
• The PR follows the style guide.
• The PR does not contain any unnecessary code changes from Android Studio (reference).
• The PR is made from a branch that's not called "develop" and is up-to-date with "develop".
• The PR is assigned to the appropriate reviewers (reference).

For UI-specific PRs only

If your PR includes UI-related changes, then:

• Add screenshots for portrait/landscape for both a tablet & phone of the before & after UI changes
• For the screenshots above, include both English and pseudo-localized (RTL) screenshots (see RTL guide)
• Add a video showing the full UX flow with a screen reader enabled (see accessibility guide)
• For PRs introducing new UI elements or color changes, both light and dark mode screenshots must be included
• Add a screenshot demonstrating that you ran affected Espresso tests locally & that they're passing

[Tejas-67]

@adhiamboperes the tests are failing because of the increase in bundle size by 1 due to addition of screen density value.
modifying the expected bundle size in the tests would fix this. Should I go with this fix?

[Tejas-67]

@adhiamboperes please check

[adhiamboperes]

@adhiamboperes the tests are failing because of the increase in bundle size by 1 due to addition of screen density value. modifying the expected bundle size in the tests would fix this. Should I go with this fix?

Hi @Tejas-67, I took a look -- yes, modifying the expected size in tests should be the correct way to address this.

[Tejas-67]

@adhiamboperes please check

[Tejas-67]

@adhiamboperes

[oppiabot]

Hi @Tejas-67, I'm going to mark this PR as stale because it hasn't had any updates for 7 days. If no further activity occurs within 7 days, it will be automatically closed so that others can take up the issue.
If you are still working on this PR, please make a follow-up commit within 3 days (and submit it for review, if applicable). Please also let us know if you are stuck so we can help you!

[adhiamboperes]

Thanks @Tejas-67!

I have left an improvement suggestion but the overall approach is in the right direction. PTAL.

[oppiabot]

Hi @Tejas-67, I'm going to mark this PR as stale because it hasn't had any updates for 7 days. If no further activity occurs within 7 days, it will be automatically closed so that others can take up the issue.
If you are still working on this PR, please make a follow-up commit within 3 days (and submit it for review, if applicable). Please also let us know if you are stuck so we can help you!

[adhiamboperes]

@Tejas-67, any update on this? Please assign this PR to me once it ios ready for a final review.

[Tejas-67]

hey @adhiamboperes, i have done the necessary changes. Please check.

[adhiamboperes]

Thanks @Tejas-67. This LGTM.

[oppiabot]

Assigning @BenHenning for code owner reviews. Thanks!