Config command

[Keyrxng]

Resolves #888 & #887

Will cover E2E tests over the weekend

Quality Assurance:

• Comments: config command ubq-testing/bot-ai#23 (comment)
• Commits: https://github.com/ubq-testing/bot-ai/commits/main

[netlify]

❌ Deploy Preview for ubiquibot-staging failed.

Name	Link
🔨 Latest commit	a2ec9fa
🔍 Latest deploy log	https://app.netlify.com/sites/ubiquibot-staging/deploys/6558b6a1e9e20c000896a100

[Keyrxng]

@pavlovcik Forgive the noobness here but is this the best way to merge from your current refactor branch? Seeing all of those commits gives me the fear but I expect once merged it shouldn't make a difference or is this a disaster? 🤣

[0x4007]

I don't understand your question but technically speaking we don't have tasks open for contributors on this repository because of the anticipated complexities with merging. If you're particularly motivated to try even with this relatively adversarial merge environment (refactor is the top priority) then I would recommend you base your branch off of the latest, which actually is feat/contributor-incentives-total-scoring

For context, I'll try risky changes on a sub-branch, get them pretty stable, then merge to my main branch. In the context of the refactor, my "main branch" is refactor/general