Have projects import trimmed URIs

[philderbeast]

Fixes #10622. Trims URIs before parsing them with parseURI. If any project config path doesn't equal its trimmed self then it is displayed quoted so that the whitespace is obvious.

---

Template Α: This PR modifies behaviour or interface

Include the following checklist in your PR:

• Patches conform to the coding conventions.
• Any changes that could be relevant to users have been recorded in the changelog.
  • Is the change significant? If so, remember to add significance: significant in the changelog file.
• The documentation has been updated, if necessary.
• Manual QA notes have been included.
• Tests have been added. Yes doctests and cabal-testsuite tests.

[ulysses4ever]

Will need a changelog but otherwise it looks like the right direction overall.

[geekosaur]

Huh. First time I've seen RTD fail that way.

[philderbeast]

Huh. First time I've seen RTD fail that way.

And I didn't change the docs. @geekosaur, other CI jobs I can restart but not that one.

[geekosaur]

That's normal, since RTD isn't actually part of GitHub Actions. You'll need to change something somewhere to trigger a new build, though. (You may want to hold off a bit though, to let RTD fix whatever's wrong on their end.)

[philderbeast]

@geekosaur I've included a W3C quote about URLs in the changelog and added the bug label to this pull request as it fixes a bug.

[philderbeast]

@Mikolaj this is a bug fix in need of a second reviewer. Do you think we can get it into the upcoming release?

[geekosaur]

Uh, what upcoming release? I'm not sure it qualifies for 3.14.1.1.

[philderbeast]

@geekosaur I had a hunch there was a release coming up based on bumped version numbers and pull requests being expedited. Is there somewhere where plans for upcoming releases are posted?

[geekosaur]

The recently bumped version number was actually missed for 3.14.1.0, and is currently being considered severe enough that we'll push a 3.14.1.1 quickly. But as I understand it, we aren't planning to include any other fixes, just this mistake.

The expedited pull requests are all for the cabal-head prerelease from CI, which has been broken since August except for a single update in October. Its only relationship to releases is to make new features in HEAD available before the next release. Oh, and also for development versions to have commit information in them, which again has nothing useful to do with releases (it's specifically disabled for them).

[Mikolaj]

LGTM

@Kleidukos is the 3.14.* release manager so up them if/when to include this fix.

[Kleidukos]

Why not include it for a cabal 3.14.2.0, but not for 3.14.1.1 :)

[philderbeast]

Label merge+no rebase is necessary when the pull request is from an organisation.