Publish installable default plugins to Store

[jjw24]

Context:
Allows the user to reinstall a default plugin from the Store instead of having to reinstall flow entirely.

Changes:

• All default plugins have their own repo for holding their releases
• Use workflow to publish plugins to their repo if their plugin.json is modified
• The actual installation code checks a plugin's ID against a list of default plugin IDs, if matches a default plugin's ID the install directory is changed to the program directory's plugin folder instead of the usual UserData location. This ensures that when flow is updated the default plugins are also reinstalled, otherwise if placed in UserData directory then will end up with duplicate default plugins.

Tests:

• Workflow only runs when changes are detected in Plugins folder
• Default plugins are published to their respective repositories when their plugin.json has been modified
• Default plugins are not published if their plugin.json has not been modified
• All installed default plugins work as expected
• A default plugin is installed in the program's directory instead of userdata's plugin directory

Close #1984

[github-actions]

@check-spelling-bot Report

🔴 Please review

See the 📂 files view or the 📜action log for details.

Unrecognized words (3)

alreadyexists
CETYU
noresult

To accept ✔️ these unrecognized words as correct and remove the previously acknowledged and now absent words, run the following commands

... in a clone of the [email protected]:Flow-Launcher/Flow.Launcher.git repository
on the deploy_plugins branch (ℹ️ how do I use this?):

curl -s -S -L 'https://raw.githubusercontent.com/check-spelling/check-spelling/main/apply.pl' |
perl - 'https://github.com/Flow-Launcher/Flow.Launcher/actions/runs/5931862752/attempts/1'

To have the bot do this for you, reply quoting the following line:
@check-spelling-bot apply updates.

If the flagged items are 🤯 false positives

If items relate to a ...

• binary file (or some other file you wouldn't want to check at all).

  Please add a file path to the excludes.txt file matching the containing file.

  File paths are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your files.

  ^ refers to the file's path from the root of the repository, so ^README\.md$ would exclude README.md (on whichever branch you're using).

• well-formed pattern.

  If you can write a pattern that would match it,
  try adding it to the patterns.txt file.

  Patterns are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your lines.

  Note that patterns can't match multiline strings.