Some processes that can be improved in Otter dev work

Some processes in the Otter dev work that can be improved (for my rock for this Quarter).

1. Php standard

PHPCS does not work with PHP 7.4 or later. Many times we push the code and then fix the PHPCS errors after we see them in the PR checks.

2. Bem helper

We could start adding CSS classes with BEM in mind. It will make the CSS files look better and maybe make the overall CSS size smaller.

A nice touch here would be to implement a BEM helper that will generate class names, something like react-bem-helper
or even use that package, but implementing it should be fairly easy.

3. PHP tests

Some additional PHP tests might be helpful.

4. Otter child plugins usage

Right now, when developing the Otter repo, we can build and use only the entire Otter plugin. So, if we need for example just the Block CSS plugin, we need to take it separately and move it to another instance, which takes unnecessary time. Maybe we can improve this.

Feedback is appreciated @Codeinwp/otter-team.

The issue proposes four separate areas: PHPCS compatibility, BEM class-name support, additional PHP tests, and a workflow for using Otter child plugins independently. Start by choosing one area and reviewing the current development and test setup; done should be defined as a specific, tested improvement rather than addressing all four proposals.