Logged in users are unable to view preserved formats of links on public collections

[SapphicMoe]

Describe the bug Preserved formats of links (screenshots, archived versions of links, etc) that are shared on a public collection are unable to be viewed on a logged in account.

To Reproduce Steps to reproduce the behavior:

1. Create a new link, for example, https://docs.astro.build
2. Create a collection
3. Go to the newly created collection
4. Click on the three dots on the far right on the collection page, and select "Share and Collaborate"
5. Enable the "Make this a public collaboration" checkbox, and click "Save Changes"

Expected behavior A logged in user views a public collection that was shared to them by another user, selects the https://docs.astro.build link, clicks the "Preserved Formats" button by using the three dots next to the link, and chooses the external link button for the preserved screenshot format. The user views the preserved screenshot of the https://docs.astro.build link.

Actual behavior A logged in user views a public collection that was shared to them by another user, selects the https://docs.astro.build link, clicks the "Preserved Formats" button by using the three dots next to the link, and chooses the external link button for the preserved screenshot format. All the user gets is a blank page.

Developer Tools reports the following error:

- GET https://links.internal.network/api/v1/links/2 401 (Unauthorized)

- Uncaught (in promise) Error: Collection is not accessible.
    at Object.mutationFn (598-d13c8268529e7869.js:1:12333)

Screenshots

Desktop (please complete the following information):

• OS: [e.g. iOS] Microsoft Windows 11 Version 23H2 (OS Build 22631.4317)
• Browser [e.g. chrome, safari] Microsoft Edge
• Version [e.g. 22] Version 130.0.2849.56 (Official build) (64-bit)

Smartphone (please complete the following information):

• Device: [e.g. iPhone6] OnePlus 9 5G
• OS: [e.g. iOS8.1] Android 14
• Browser [e.g. stock browser, safari] Microsoft Edge
• Version [e.g. 22] Version 130.0.2849.57

Additional context Add any other context about the problem here.

[daniel31x13]

This issue will be fixed in the next release.