Make automated edits of Author/People pages less error-prone

[claremacrae]

When update_releases.py is used to update existing author, plugin and theme pages there is a tedious set of manual checks and reversions to be done...

These reversions are not documented, which limits the number of people who can do this step to essentially @claremacrae and @argenos.

This issue is to record the steps needed to remove as many of those manual edits as possible.

See also #166 (Make manual edits of Author/People pages less error-prone) which is about things like streamlining the formatting of links in the author template, to make adding things like sponsorship links easier.

For the background to this, see the Content: People page.

[claremacrae]

The following are the bits of People pages that get automatically updated content:

1. Sometimes the website e.g.

- Website: <https://github.com/Signynt> ^website

2. Lists of plugins and themes:

%% Begin Hub: Released contributions %%
...
%% End Hub: Released contributions %%

3. Different spellings of the author name in different manifest files by the same author

[claremacrae]

Things that interfere with the updating of the above information:

1. Flickering, random changes of the author URL, due to repo URLs being used as the authorURL in the manifest, and the author publishing new plugins
2. Plugins which have been removed from community releases being still listed in the author's Plugins list, such as obsidian-footnotes and pdf-to-markdown-plugin by akaalias
   • Suggestion: move links to any no-longer supported plugins to a new 'Deprecated plugins' section in the author note, so the link is still present in the author note, but it does not need to be reverted every time a full update of hub content is done. This naming is constant with that proposed in Detect if plugin has been deprecated and move to new "Discontinued plugins" #162
3. Plugins having more than one author
4. Customisations, such as "buy me a coffee" links and "twitter account" links, that are overwritten with text from the author template each time a full update of the hub content is done
   • Suggestion: Divide up author.md.jinja in to sections, as has been done for themes and plugins - so that the section delimited by %% Begin Hub: Released contributions %% and %% End Hub: Released contributions %% can be over-written, without interfering with the rest of the file's potentially manually updated content.
5. Full path being needed to disambiguate links between an author and theme whose files have the same name - see Script the special case of hipstersmoothie and other duplicate file names #143

[claremacrae]

A not-yet-documented component of this is changing update_releases.py --overwrite so that it only selectively updates only the parts of author notes that contain no human edits, such as the lists of published plugins and themes.

[argenos]

From our pairing session on saturday:

• On websites, ignore any that begin with github.com (duplicated info already in the template) or obsidian.md (failed to update manifest.json)
• add a check to verify plugin names are not obsidian (incorrectly or missing update to manifest.json from template)
• Make discord handle an alias instead of part of the note (will make it easier to find related notes or unlinked mentions from the roundup)
• Group author information according to the way it's added: manual (publish) and what is added by our scripts (github link, website if present in manifest.json)

[argenos]

Related: #217