Add abandoned flag for plugin json

[kalilistic]

Add a new bool on plugin json - isAbandoned that defaults to false.

When a developer plans to no longer update a plugin, someone can PR a json update to flip it to true. This would allow us to generate a list of all plugins that need adoption. Users can refer to this list to know what plugins are just pending updates vs. which ones are ded (for the time being at least).

Credit to Arc on the flag idea.

[kalilistic]

Could also have a dalamud assets file like how banned versions are handled too.

[kalilistic]

Working on this.

[kalilistic]

Summary for discord brainstorm session.

Changes

• Add maintainers[] and DevSupportState to plugin json.
• Create unsupportedplugins.json in assets.
• State set by plugin.json can be overriden by unsupportedplugins.json
  • this will allow easier central management of marking plugins as unsupported without a bunch of PRs
• Show messages in Plugin Installer if state is anything other than Active (default).
• Maintainers array will replace author in Plugin Installer.
• Maintainers array represents anyone who can make PRs for the plugin as the contact point.

DevSupportState Enum ACTIVE - new updates/features MAINTENANCE_ONLY - only bug fixes, stable PRE_RELEASE - early alpha/testing release only ADOPTABLE - waiting for new dev to give it a home OBSOLETE - replaced by vanilla feature, other plugin DISCONTINUED - against current rules or dev reasons

Examples: // discontinued plogon { "name": "Oops! All Lalafells", "author": "Avaflow", "maintainers": [], "state": "DISCONTINUED", "reason": "developer doesn't want to support anymore." }

//worky plogon { "name": "XIVDeck", "author": "kazwolfe", "maintainers": ["kazwolfe", "reiichi001"], "state": "MAINTENANCE_ONLY", "reason": "I do not have the spare time to work on future features." }

[kalilistic]

Closing as stale. This concept may come back up as part of the plugin installer refresh DIP.