Use structural pattern matching to handle linkcheck result statuses

[jayaddison]

Feature or Bugfix

• Refactoring (and a legacy code cleanup)

Purpose

• The repeated [el]if...result.status == <status> conditions in part of the linkcheck code expose an intended behaviour: each status code implies that the code should follow one particular code path to handle the result. This seems like a good fit for a match clause, available from Python3.11+.

Detail

• Handle linkcheck status codes using a match statement.
• Also includes a tangential refactor of some logging code, to fit the resulting code within formatting guidelines while remaining aesthetically reasonable.
• For review purposes, it could be helpful to ignore whitespace differences introduced by this changeset (w=1 query-string parameter, if using the GitHub web comparison interface).

Relates

• Builds upon #13043.

[jayaddison]

@AA-Turner changelog entry required, do you think?

[AA-Turner]

There's no visible behaviour change to users so I shouldn't think one is required.

[AA-Turner]

Thank you @jayaddison!

A

[jayaddison]

Brilliant! Thank you for the code reviews!

[AA-Turner]

It seems 'local' is currently unused, by the way.

[jayaddison]

Mmm. As is the linkstat['text'] assignment.

For local -- perhaps that should become part of a separate link property that indicates whether each link is local or remote. I'll think about that and file a change suggestion / feature description at some point.