💥 Sensors API breaking changes

[apalala-dev]

Description

SensorConfig already contained:

• list of sensors
• flash mode
• aspect ratio
• zoom
• mirrorFrontCamera

Now it has single and multiple constructors to set one or multiple sensors. The parameters that SensorConfig already contain have been removed from CameraAwesomeBuilder.

Now, one could use CamerAwesome like this:

CameraAwesomeBuilder.awesome(
     saveConfig: SaveConfig.photoAndVideo(
      photoPathBuilder: () => path(CaptureMode.photo),
      videoPathBuilder: () => path(CaptureMode.video),
      initialCaptureMode: CaptureMode.video,
    ),
    sensorConfig: SensorConfig.single(
      sensor: Sensor.position(SensorPosition.back),
      flashMode: FlashMode.auto,
      zoom: 0.5,
      aspectRatio: CameraAspectRatios.ratio_1_1,
      mirrorFrontCamera: true,
    ),
)

Or even:

CameraAwesomeBuilder.awesome(
     saveConfig: SaveConfig.photoAndVideo(
      photoPathBuilder: () => path(CaptureMode.photo),
      videoPathBuilder: () => path(CaptureMode.video),
      initialCaptureMode: CaptureMode.video,
    ),
);

In this case, the default configuration is used (back sensor, no flash, no zoom, aspect ratio 4:3, mirroFrontCamera = false).

Notes:

• Changing parameters of SensorConfig (e.g.: flash) call native code to make the change.
• If the SensorConfig is not the currently used SensorConfig, it might have unpredictable behaviour.
• The initial parameters of SensorConfig builder don't actually call native code since the camera might not have been setup yet.

Next step: make SaveConfig compatible with web and multi camera.

Checklist

Before creating any Pull Request, confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).

• [x] 📕 I read the Contributing page.
• [x] 🤝 I match the actual coding style.
• [x] ✅ I ran flutter analyze without any issues.

Breaking Change

• [x] 🛠 My feature contain breaking change.

CameraAwesomeBuilder now takes a SensorConfig instead of the several parameters it already has.