Fix _load_textdomain_just_in_time warning

[malithsen]

Fixes #4085, #4140

Changes proposed in this Pull Request:

This PR fixes a warning that occurs when translations are loaded too early in the WordPress lifecycle. The warning appears as:

Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce-gateway-stripe domain was triggered too early.

The issue was introduced when the Status page updates were added in #3878, which instantiates the payment gateway during plugins_loaded. This caused translations to be loaded before WordPress's text domain infrastructure was fully initialized.
Initially, I considered moving the entire plugin initialization from plugins_loaded to init. While that fixed the error and should avoid any future instances that could lead to similar errors, it would have been too broad of a change with potential side effects.
Instead, this PR proposes a more targeted fix of only initializing the status page updates during init.

This ensures:

• Translations are loaded at the correct time (priority 10)
• Status page is initialized after translations (priority 15)
• Only the Status page functionality is affected,

Testing instructions

To reproduce the error:

1. Switch to develop.
2. Enable debugging by adding define( 'WP_DEBUG', true ); to your wp-config.php
3. Change site language to English (UK) via Settings -> General -> Site Language.
4. Go to Dashboards -> Updates. Click on "Re-install version 6.7.2–en_GB"
5. Notice the warning on top of the page.

Test the fix:

1. Switch to this branch.
2. Above notice should no longer be visible.

Test for regressions:

Follow the instructions in #3878

---

• Covered with tests (or have a good reason not to test in description ☝️)
• Tested on mobile (or does not apply)

Changelog entry

• This Pull Request does not require a changelog entry. (Comment required below)

Changelog Entry Comment

Comment

Post merge

• Added testing instructions to the Release Testing Instructions wiki page (or does not apply)
• Added the needs docs label (or does not apply)
• Included this PR in the Release Thread scope (or does not apply)

[Mayisha]

I followed the steps to reproduce but could not reproduce the error in develop 🤷
But the changes look reasonable and it should fix the issue. Approving,