Generating a share link can cause QR code rendering to fail

[achingbrain]

The QR code renderer has a size limit based on the size of the image.

If we append the browsers' multiaddrs to the link it can exceed this limit (due to multiple relay addresses, certificate fingerprints, etc) and cause the page to crash.

Increasing the allowed size of the QR code fixes this but the QR code becomes illegible and it may continue to be an issue depending on the relay addresses the browser manages to acquire.

Instead we should publish the provider record for uploaded files (either manually or via a delegate) and let remote peers look up the browser address instead of appending it to the URL.

[welcome]

Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment.
Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:

• "Priority" labels will show how urgent this is for the team.
• "Status" labels will show if this is ready to be worked on, blocked, or in progress.
• "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.io if you just need general support.