Intent System

[ChristianMurphy]

This would add an additional layer of abstraction over the current task system.
Allowing a recipe to register an intent, and server plugins could offer the service.
For example a 'Repository' intent could be answered by a Github, Bitbucket or Gitlab plugin.

Currently the abstraction is

• Recipe - High Level Actions or Groups of Actions
• Resource - Abstraction over a local or remote service

New abstraction would likely look like

• Recipe - Flow control between tasks
• Tasks/Activities - High level actions, such as 'add users to repo'
• Resource - Abstraction over a local or remote service

This would be a platform change to attempt to simplify and future proof the code.

Challenges
This would bring back the challenge that brought me to the Resource/Recipe pattern in the first place.
How would independent plugins register requirement or mutual exclusivity?
While maintaining loose coupling?

For example Github issues requires a Github repo.
And Github issues are mutually exclusive to a Bucket repo.

Related to #5

ref https://developer.android.com/guide/components/intents-filters.html