Drop 128x160 ESP-32 camera resolution

[oxan]

What does this implement/fix?

Since the addition of OV5640 support in the ESP-32 camera driver in March 2020, it no longer provides the FRAMESIZE_QQVGA2 type. This was imported in Arduino ESP32 core 1.0.5, so compilation was broken from that version onwards.

Drop the support for this resolution, as this specific resolution does not seem to be useful enough for it to be worthwhile to make it conditionally available depending on the used Arduino version (which is further complicated by the fact that Arduino doesn't provide a numeric version define).

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Configuration change (this will require users to update their yaml configuration files to keep working)

Technically this is a breaking change for users using this resolution, but I don't think we should bother to do anything about that beyond a changelog entry.

Related issue or feature (if applicable): fixes esphome/issues#1884

Pull request in esphome-docs with documentation (if applicable): esphome/esphome-docs#

Test Environment

• ESP32
• ESP8266
• Windows
• Mac OS
• Linux

Example entry for config.yaml:

N/A

Explain your changes

It fixes compilation.

Checklist:

• The code change is tested and works locally.
• Tests have been added to verify that the new code works (under tests/ folder).

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated in esphome-docs.

[oxan]

I also added the ESP-32 camera to one of the test YAML files, so that it'll at least get compile tested in CI from now on in the hopes that'll catch similar breakage faster from now on :)

[agners]

This actually fixes compiling the Camera component with Arduino SDK 1.0.6.

[oxan]

This is esphome/esphome-docs#1192 btw, I see I forgot to fill in the PR number.