tests/test_repo_hygiene.py: ONE_LINE_INSTALL_IN holds neither docs/release-notes/v1.1.0.md nor v1.1.1.md, so a mistyped one-line install in either passes #885

Goal: every release note that carries the one-line install is held to it byte for byte, as README.md, the handbook and v1.0.1.md are.

Filed by lane openRepoShape-1. It is the test-cover point of lane 3's review RV883 of #883, the v1.1.1 release notes (#883, comment): "ONE_LINE_INSTALL_IN (tests/test_repo_hygiene.py:1567) holds neither v1.1.0.md nor v1.1.1.md. Mutant M1 survives, so this belongs in a separate test PR."

What is wrong. test_the_one_line_install_is_the_same_everywhere holds each file in ONE_LINE_INSTALL_IN (tests/test_repo_hygiene.py:1566-1567, at main 33c5128b) to carry ONE_LINE_INSTALL byte for byte. That is curl -fsSL https://github.com/opensoft/openRepoShape/releases/latest/download/install.sh | bash. The list holds five files:

• install.sh;
• openRepoShape;
• README.md;
• docs/handbook.html;
• docs/release-notes/v1.0.1.md.

Two release notes carry the line once each and are not in the list:

• docs/release-notes/v1.1.0.md;
• docs/release-notes/v1.1.1.md, added by docs/release-notes/v1.1.1.md: the v1.1.1 release notes, for the issues landed so far #883, which lands last as the v1.1.1 release commit.

A mistyped copy in either passes. RV883's mutant M1 is that case, and it survives.

The fix, tests only. Either of these:

• add docs/release-notes/v1.1.0.md to ONE_LINE_INSTALL_IN now, and docs/release-notes/v1.1.1.md once docs/release-notes/v1.1.1.md: the v1.1.1 release notes, for the issues landed so far #883 has landed;
• or have the test find every docs/release-notes/*.md that names releases/latest/download/install.sh, and hold each one. This covers each later release's notes with no edit.

Lane 3, the release owner, places it. Lane 1 can take it.