Normalize and provide automatic metadata for arXiv links

[NattyNarwhal]

If I post an arXiv link, there's some concerns:

• The summary link vs. the PDF link, which should be used?
• You have to copy and paste the summary for a PDF to have working abstracts for people who have descriptions inline.
• If you're posting a PDF link, you probably want to post a link back to the summary for more detail

I propose special-case handling for arXiv. arXiv exposes an API. We can extract the ID from the link, and generate a query URL that returns the metadata in a structured form (i.e. http://export.arxiv.org/api/query?id_list=2303.05498&max_results=1 from the original URL https://arxiv.org/pdf/2303.05498.pdf). It outputs slightly spicy Atom. We can use that to extract the summary for a PDF link, include a link to the summary in the article body, add a year in the title if the paper isn't from the current year, and link the PDF.

[pushcx]

Sounds like a great quality-of-life feature, we get a lot of links to arXiv.

Whoever picks this up - start from StoriesController. the fetch_url_attributes action. It's the endpoint powering the Fetch Title button.

Huh. That has me wondering if the Fetch Title button works for users with js disabled. From a glance at the action, probably not. That'd be a nice improvement as part of this, and off the top of my head it might be as easy as having that button submit to the preview action.

[pushcx]

Recognizing duplicate/alternate links was handled in #965 / 9041e3d. These other features would still be nice improvements!