[ADD] Database command to change database parameters without starting it

[brinkflew]

Description

Allow changing states and parameters of a local database without running it:

• change or remove linked worktree
• change or remove linked virtual environment
• change or remove linked repository
• (un)whitelist

Linked Issues

• closes Impossible to link database and repository #101

Compliance

• I have read the contribution guide
• I made sure the documentation is up-to-date both in doctrings and the docs directory
• I have added or modified unit tests where necessary
• I have added new libraries to the requirements.txt file, if any
• I have incremented the version number according the versioning guide
• The PR contains my changes only and no other external commit

[lse-odoo]

functionallity speacking, would it make sense to also have a command to get the actual current data ? for example giving:
odev database test repository
would give the current directory while:
odev database test repository "lse-odoo/repository"
would set its value

[brinkflew]

functionallity speacking, would it make sense to also have a command to get the actual current data ? for example giving: odev database test repository would give the current directory while: odev database test repository "lse-odoo/repository" would set its value

So more like the odev config command, that could indeed make sense but I'm afraid this would be too much of a duplicate with odev info and odev ls that already prints those. Maybe the best would be to edit odev info so it could set values and not only print them, but some of those won't be editable and I'm not sure how to make that clear a field can or cannot be changed...

[lse-odoo]

functionallity speacking, would it make sense to also have a command to get the actual current data ? for example giving: odev database test repository would give the current directory while: odev database test repository "lse-odoo/repository" would set its value

So more like the odev config command, that could indeed make sense but I'm afraid this would be too much of a duplicate with odev info and odev ls that already prints those. Maybe the best would be to edit odev info so it could set values and not only print them, but some of those won't be editable and I'm not sure how to make that clear a field can or cannot be changed...

I feel like it's becoming more and more complicated personally. The more command we add, the more the complexity it gets. The ideas are good in themselves, but I guess it can become complicate for a new comers.
It's arguable if odev ls or having odev database --list would make more sense for instance. odev info can work without having the database locally so is a bit different, but it could be interesting to have kind of like aliases (to avoid dropping "old" commands). For example the odev database --list command mentioned before (that internally would just call odev ls. We could also have odev database blabla.odoo.com --info (or without --info) that would word like odev info but here we knows that the database is locally restored.

I am also wondering if "database" command name should be rather rename "local-database" as here all commands make sense only for database installed locally, it might avoid ambiguity on the scope of the action.

In the long term I feel that having "group" of commands might make sense in odev to avoid having 10 000 commands listed in help and have a better separation of the "category" of commands (even if it would be arguable in which category belongs which command). This would make sense with plugin in my opinion as generally they include commands for a given scope/category. Here for example being in the group "local-database" so that any odev command have to be prefixed with "local-database" before calling the real command "info, list, etc." could make sense