Create add/remove config logic

[0x4007]

1. We need to be able to select which ubiquibot-config.yml to edit, so we at minimum need an organization picker after GitHub authentication.
2. We need to parse the YML file, and target the config based on the plugin's URL/location. Then edit the YML file and push the commit using the user's credentials.

More thoughts on the readme.

LLM

Without research, the lazy answer is that LLMs can easily solve the problem. We could even consider passing in the most important/relevant files of the plugin so that the LLM can figure out all the default values and other miscellaneous details.

But it would certainly be preferred to implement this with traditional code. I think with a bit of research it can be pretty straightforward.

[Neuman-Nz]

/help

[ubiquity-os-beta[bot]]

Available Commands

Command	Description	Example
/help	List all available commands.	/help
/allow	Allows the user to modify the given label.	/allow @user1 label
/query	Returns the user's wallet, access, and multiplier information.	/query @ubiquibot
/start	Assign yourself to the issue.	/start
/stop	Unassign yourself from the issue.	/stop
/wallet	Register your wallet address for payments.	/wallet ubq.eth

[ubiquity-os[bot]]

Available Commands

Command	Description	Example
/help	List all available commands.	/help
/allow	Allows the user to modify the given label.	/allow @user1 label
/query	Returns the user's wallet, access, and multiplier information.	/query @ubiquibot
/start	Assign yourself to the issue.	/start
/stop	Unassign yourself from the issue.	/stop
/wallet	Register your wallet address for payments.	/wallet ubq.eth

[Neuman-Nz]

/start

[ubiquity-os[bot]]

! Please set your wallet address with the /wallet command first and try again.

[ubiquity-os[bot]]

! No wallet address found

[0x4007]

@gentlementlegen can you fix the double post?

[gentlementlegen]

@0x4007 Spec at https://github.com/ubiquity-os-marketplace/command-start-stop/issues/60