Remove supported badges from unsupported repos

[emteknetnz]

Because module standardiser will only update supported repos, it fail to remove supported badges from the README.md of unsupported repos because it won't run script on it

Ckan registry still has a supported badge on it despite it not being supported for cms 5, though it is supported for cms 4

To decide

First we need to clarify that we indeed should not display the supported badge on things that are only supported for cms 4. If we do still want a badge then it should be a different badge IMO that says supported for security only

Acceptance criteria

• Update module-standardiser to remove the supported badge from unsupported modules.
• Only the CMS 5 branches should be updated.
• All modules that lost their supported status in CMS 5 should loose their badge.

PRs

• NEW Remove supported badge from unsupported modules module-standardiser#58
• MNT Run module-standardiser cwp#338
• MNT Run module-standardiser cwp-core#132
• MNT Run module-standardiser cwp-search#62
• MNT Run module-standardiser silverstripe-akismet#49
• MNT Run module-standardiser silverstripe-ckan-registry#312
• MNT Run module-standardiser comment-notifications#58
• MNT Run module-standardiser silverstripe-comments#389
• MNT Run module-standardiser silverstripe-content-widget#39
• MNT Run module-standardiser silverstripe-crontask#90
• MNT Run module-standardiser silverstripe-fulltextsearch#358
• MNT Run module-standardiser silverstripe-graphql-devtools#54
• MNT Run module-standardiser silverstripe-postgresql#151
• MNT Run module-standardiser silverstripe-sqlite3#76
• MNT Run module-standardiser sspak#97
• MNT Run module-standardiser silverstripe-widgets#212

[maxime-rainville]

I'm happy to remove badges once support is dropped by the latest major.

I guess if we want to be especially formal about this, we could remove the badge from the default branch, but keep it on the branches where the module was supported.

[GuySartorelli]

PRs merged