Build: Improve Makefile rules related to kernels

Context

Owner: @vch9

The definitions of the Makefile rules related to the kernels forces Tezos developers to install too many dependencies to be able to run all the Tezt scenarios.

Building a kernel should not require to install the Rust formatter or clippy, for instance.

We revisit a bit globally the makefile definitions to make the separation between building and enforcing code quality more explicit (basically following the example set by the SDK). Besides, we use this opportunity to clean-up a bit the names and some inconsistencies.

The overall developer experience should be improved.

This is orthogonal to !8203 (closed)

Manually testing the MR

As someone only willing to run Tezt scenarios,

make build-kernels-deps
make build-kernels

should be enough.

As someone wanting to hack the EVM kernel or the rollup SDK

make build-kernels-dev-deps
make build-kernels
make check-kernels
make test-kernels

is what you are looking for.

Checklist

• Document the interface of any function added or modified (see the coding guidelines)
• Document any change to the user interface, including configuration parameters (see node configuration)
• Provide automatic testing (see the testing guide).
• For new features and bug fixes, add an item in the appropriate changelog (docs/protocols/alpha.rst for the protocol and the environment, CHANGES.rst at the root of the repository for everything else).
• Select suitable reviewers using the Reviewers field below.
• Select as Assignee the next person who should take action on that MR