Set labels command

[0x4007]

In an effort to reduce the distinction between "contributors" and "collaborators" we should let anybody whitelisted to set labels.

It may not be user friendly unless we do a mini "search" and select the highest match. For example:

/labels 15 min high priority

Then we need to intelligently pick the correct labels (or create new ones in the case of the time estimates)

We also need an admin control (maybe simpler to write in the config yml?) to let specific users set a class of labels: time, priority, price.

time:
   users:
      - 0x4007
      - whilefoo
priority: 
   users:
      - keyrxng 
price:
   users: 
      - rndquu 

This can be really nice with the natural mini LLM command router. Particularly in outside of GitHub contexts like telegram or a google docs comment:

@UbiquityOS set to 15 min high priority task

v2 vision

The reason why I want to blur the lines between collaborator/contributor is because I think the concept of a "core team" is not truly DAO like. Eventually we should allow for label classes to be editable based on XP. For example:

time:
   xp: 0
priority: 
   xp: 1000
price:
   xp: 2000

And ideally with a time decay element so that you need to be actively contributing to have the privilege to set these. And of course, collaborators would be able to set using the GitHub UI.

I can't seem to set labels. 15 minutes sounds about right

Originally posted by @whilefoo in #47 (comment)

[whilefoo]

We also need an admin control (maybe simpler to write in the config yml?) to let specific users set a class of labels: time, priority, price.

time:
   users:
      - 0x4007
      - whilefoo
priority: 
   users:
      - keyrxng 
price:
   users: 
      - rndquu 

We already store access control in Supabase which is better than storing in a config, because you can dynamically set it with a command /allow @0x4007 time

We just need to add /setLabel which LLM command router will be able to call and the plugin will set the label.