fix(NcReferenceList): Resolve relative URLs before fetching references

[mejo-]

Resolve relative URLs and those without a location using window.location before fetching references for them. This fixes e.g. getting references for relative links to other pages in Collectives.

🏁 Checklist

• ⛑️ Tests are included or are not applicable
• 📘 Component documentation has been extended, updated or is not applicable
• 3️⃣ Backport to next requested with a Vue 3 upgrade

[mejo-]

/backport to next

[Antreesy]

Breaking messages in Talk, if couldn't resolve a URL:

Loading for all messages	Failing at more-than-just-link messages

[mejo-]

@Antreesy what do you mean with "if couldn't resolve a URL"? The links in your screenshot already look like full URLs, so they shouldn't get altered by the changes from this PR. Or are links to other calls inserted as absolute links without a location part in Talk?

[Antreesy]

The links in your screenshot already look like full URLs, so they shouldn't get altered by the changes from this PR.

They're not, but new URL creates an object for every text, whether it has a link or not.
BEFORE change, there was no attempt to resolve a reference, and messages don't have the spinner
Now, if messages which includes both plain text and link, references couldn't be loaded (third example)

I'm looking into how to fix that

[mejo-]

Ah, so the problem is that that Talk passes text that contains more than just an URL to NcReferenceList. In Text, we check first if the passed text is merely an URL and only pass it in this case.