feat(lights)!: remove individual fixture requirements and constraints

[Yoronex]

Description

This PR includes a large refactor of the processing of fixture settings from colors and positions to actual DMX channel values. The new implementation uses a Strategy design pattern to neatly separate different responsibilities. Then, with the improved framework, the following features are added:

• A master dimmer channel is no longer required for RGB fixtures. When an RGB still needs to be dimmed, it is applied to the individual channels instead.
• A shutter channel is no longer required for any fixture. If the fixture still needs to strobe, this is done by switching all lights on and off within Aurora each tick.
• Each fixture has a specific number of channels it requires to function. This can save massive amounts of space on the DMX bus.
  For example, each fixture on the disco floor only needs 3 channels instead of the previous Aurora-default of 16. This allows for 170 disco floor fixtures in one DMX universe, instead of 32 (increasing the floor size from 8m2 to 42m2).
  It does include breaking changes, as multiple database columns have been renamed. This is caused by moving these columns to separate objects.

Related issues/external references

Fixes #35.
Fixes #36.
Includes refactoring work necessary for #31 and #29.

Types of changes

• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Style (Change that do not affect the functionality of the code)

[JustSamuel]

Note that if you want semantic-release to recognize this as a breaking change (major version bump) you should add the BREAKING CHANGE footer and only adding the ! indicator is not enough.