[AC-2554] Prevent calls to billing-status endpoint when feature flag is off

[amorask-bitwarden]

Type of change

- [x] Bug fix
- [ ] New feature development
- [ ] Tech debt (refactoring, code cleanup, dependency upgrades, etc)
- [ ] Build/deploy pipeline (DevOps)
- [ ] Other

Objective

As a relic of the Payment Method Warning Banners that are currently off behind a feature flag, there’s a timer in the web application that tries to make a request to the Billing Status endpoint in server and use the result to update the state. These timed calls should also be gated behind the same feature flag so we don’t clutter our network requests.

Code changes

• apps/web/src/app/app.component.ts: Combine the emission of the timer with the emission of the feature flag and filter out emissions where the feature flag is off.

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 4 lines in your changes are missing coverage. Please review.

Project coverage is 27.73%. Comparing base (37d4095) to head (bd3ee33).

❗ Current head bd3ee33 differs from pull request most recent head d70f69e. Consider uploading reports for the commit d70f69e to get more accurate results

Files	Patch %	Lines
apps/web/src/app/app.component.ts	0.00%	4 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #9032      +/-   ##
==========================================
- Coverage   27.75%   27.73%   -0.03%     
==========================================
  Files        2420     2418       -2     
  Lines       70063    69952     -111     
  Branches    13047    12987      -60     
==========================================
- Hits        19444    19399      -45     
+ Misses      49106    49054      -52     
+ Partials     1513     1499      -14     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[github-actions]

Checkmarx One – Scan Summary & Details – 9dff07ba-af03-4198-91b8-91aa10ed4d07

No New Or Fixed Issues Found

[amorask-bitwarden]

Hey @MGibson1, apologies - had to resolve a merge conflict. Can I get another stamp here when possible?