Improve Maintainer QoL

Re: #90, helpful improvements to the project itself:

* [ ] A build workflow to lint/test on localhost, currently only defined in [the GitHub Action](https://github.com/LoLei/razer-cli/blob/44517cb/.github/workflows/pythonpackage.yml#L37).
* [ ] A straightforward means to test project edits on a machine that has a production version installed.
- In the style of `setup.py develop` or pip "editable" package.
- Isolation, no risk of unintentionally importing previously installed version.
- Ability to interface with openrazer daemon as usual.
* [ ] Clarification of the openrazer dependency, i.e. what razer-cli does and what it expects from the daemon, and an editorial on what belongs in the CLI versus what should be left to a more comprehensive GUI.

Start with .github/workflows/pythonpackage.yml and compare its lint/test steps with the requested localhost workflow. Then investigate the project's setup.py or pip installation behavior and document the openrazer daemon dependency and CLI boundaries. Done means the workflow, isolated editable-install path, and dependency guidance are each defined and testable.

Written by the indexing model from the issue text.