fix(plugin-assets-retry): support output.assetPrefix with absolute url

[SoonIter]

Summary

let async-retry url calculating aligned with initial-retry

Before

only support

domain: ['https://a.com', 'https://b.com']

// or

domain: ['https://a.com/path-foo', 'https://b.com/path-foo']

if you uses below

domain: ['https://a.com/path-foo', 'https://b.com'],
max: 3

output: {
	assetPrefix: 'https://a.com/path-foo'
}

the retry contexts:

0. https://a.com/path-foo/static/js/main.js

1. https://a.com/path-foo/static/js/main.js

2. https://b.com/path-foo/static/js/main.js

3. https://a.com/path-foo/static/js/main.js

after

domains: ['https://a.com/path-foo', 'https://b.com'],
max: 3

output: {
	assetPrefix: 'https://a.com/path-foo'
}

0. https://a.com/path-foo/static/js/main.js

1. https://a.com/path-foo/static/js/main.js

2. https://b.com/static/js/main.js

3. https://a.com/path-foo/static/js/main.js

[netlify]

✅ Deploy Preview for rsbuild ready!

Name	Link
🔨 Latest commit	65edab6
🔍 Latest deploy log	https://app.netlify.com/sites/rsbuild/deploys/67542466f00c8300086af5d6
😎 Deploy Preview	https://deploy-preview-4129--rsbuild.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 74 (🟢 up 3 from production) Accessibility: 97 (no change from production) Best Practices: 100 (no change from production) SEO: 100 (no change from production) PWA: 60 (no change from production) View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[chenjiahan]

Is this originalQuery param the same as const originalQuery in L247?

[SoonIter]

yes, these two functions are exactly the same now

[chenjiahan]

But the originalQuery param seems to be unnecessary in this file