New Checkout experience won't load asset files if the plugin is symlinked

[laurelfulford]

Describe the bug
When the WooCommerce Stripe Gateway is symlinked and the new checkout experience is enabled, none of the assets (images, CSS, JS) load on the front-end.

To Reproduce
Steps to reproduce the behavior:

1. Set up a test site with the WooCommerce Stripe Gateway plugin symlinked rather than installed directly in the wp-content/plugins directory.
2. Turn on the new checkout experience.
3. Run through a checkout; note that the Stripe form doesn't load on the Payment Info section. In the console, there are 404 errors for the upe_ files.
4. Turn on the legacy checkout experience.
5. Repeat step 3; note that the Stripe form loads again.

Expected behavior
That the assets would load for the new checkout experience when the plugin is symlinked.

Screenshots

The screenshot is from a test site, but this originally was reported from a live site, and can be recreated when Stripe is and is not in test mode.

Environment (please complete the following information):

• WordPress Version: 6.5.4
• WooCommerce Version: 8.9.2
• Stripe Plugin Version: 8.3.1
• Browser [e.g. chrome, safari] and Version: All
• Any other plugins installed: I can recreate with just WooCommerce and the Stripe Gateway installed.

[claudiulodro]

In terms of immediate impact, this affects all WP Cloud sites that use a symlinked version of the Stripe gateway.