fix(client): don't inject queries for data URLs (fixes #2658)

[g-plane]

Description

Make it not inject queries for data URLs.

Fixes #2658

Additional context

Appending queries to data URLs (those URLs that start with data: or blob:) will break the data because data is encoded as string. This PR adds a detection for data URLs, and it will return those URLs as-is.

Is this direction right?

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

Before submitting the PR, please make sure you do the following

• Read the Contributing Guidelines.
• Read the Pull Request Guidelines and follow the Commit Convention.
• Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
• Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
• Ideally, include relevant tests that fail without this PR but pass with it.

[g-plane]

I don't know why the tests would fail.

[g-plane]

@Shinigami92 All tests passed now.

[g-plane]

@patak-js Would you like to review this PR?

[patak-dev]

We'll need @yyx990803 input here, as I don't fully understand if this change will end up affecting other parts of the system.

But I think that we shouldn't be bailing out inside of injectQuery because if you called that function, it means that you need that query to be injected in that URL. So IMO we should do this check out of injectQuery to be explicit about this

[yyx990803]

The only place the client-side injectQuery is used is by the code injected by importAnalysis here, where the URL may be fully dynamic, so we can't reliably skip the injection via static analysis. Doing the check on client makes sense.

[DenizUgur]

Sorry to bring up an old PR but it seems like this change has been reverted. Any reason why this has been done? Or is there an another way of disabling the injectQuery import?

[patak-dev]

@DenizUgur please create an issue with a minimal reproduction and more context of your problem, (you can link to this PR as additional info) so we can properly track your report