feat: command parsing

[gentlementlegen]

Resolves https://github.com/ubiquibot/plugins-wishlist/issues/6

[github-actions[bot]]

Lines	Statements	Branches	Functions
	80% (4/5)	100% (0/0)	66.66% (2/3)

JUnit

Tests	Skipped	Failures	Errors	Time
1	0 :zzz:	0 :x:	0 :fire:	3.836s :stopwatch:

Coverage Report (80%)

File	% Stmts	% Branch	% Funcs	% Lines	Uncovered Line #s
All files	80	100	66.66	80
main.ts	80	100	66.66	80	9

[gentlementlegen]

What is going on here

• added release-please
• Supabase types are now generated by the Action on build to avoid un-synched data
• fixed and improved the command parsing when using /allow
• removed defaultLabels in the configuration that was unused so far
• fixed Supabase migration files
• added tests related to the command parsing

For this plugin to work, I had to spin up another db, which I guess makes sense since we were talking about splitting the data for each plugin. However this db is under my own credentials, for testing purposes. You can find some tests commands here https://github.com/Meniole/bot/issues/4#issuecomment-2102861633

In this case maybe having a simple Cloudflare KV would suffice as it just remembers a label list for a certain user (except billing manager / admins), which seems trivial enough to be stored within a key / value pair. I could have a look at this in a separate PR, I know that would make @0x4007 very happy.

In the meantime this gives the capability to:

• set tags regarding priority and estimates
• update pricing accordingly
• allow / un-allow certain users on certain tags

Thank you @whilefoo for the heavy lifting.

[0x4007]

• removed defaultLabels in the configuration that was unused so far

They should be used to automatically populate a repository's labels with the "special" price related labels.

Do you recall when working on a new repository that you must toggle some label for the bot to populate the rest? @gentlementlegen

[gentlementlegen]

@0x4007 It is working that way, thought it would be redundant with the labels section which seems to contain the same value. See an example of configuration here. Wouldn't labels and defaultLabels be the exact same? Removed it because defaultLabels was never reference in the code either.