Add ayab-esp32 Build environment

[dl1com]

This Pull Request adds support to communicate with the new ayab-esp32 hardware platform.
Functionality is the same as with Arduino Uno

Still To Do:

• Fill in the pin numbers for the ayab-esp32 board in board.h
• Implemented board definition file
• Add code to support using comparator EOL markers.
• Implement MCP23017 support
• Test on Hardware

[github-actions]

Test Results

104 tests  ±0   104 ✅ ±0   0s ⏱️ ±0s
104 suites ±0     0 💤 ±0 
104 files   ±0     0 ❌ ±0 

Results for commit 4eb13fe. ± Comparison against base commit c6c1b2a.

♻️ This comment has been updated with latest results.

[VIPQualityPost]

New Adafruit MCP23017 library has support for both MCP23017 and MCP23008. I did not lock the version but we can do this if necessary. Removed git submodules.

[VIPQualityPost]

I think we should merge this as-is. The PR is for build environment which I think is good to go.
After this: one PR for refactor EOL code to support analog + comparator, and another for cleaning up pin names/ hardware interfaces.

[dl1com]

Seems the CI still sees the .gitmodules file although it has been deleted. Let's give it a try and merge, worst case we have to fix it after merge... :-/

[dl1com]

@t0mpr1c3 could you please review the PR so we can merge? I can't as I am an author to this PR as well.

[t0mpr1c3]

@t0mpr1c3 could you please review the PR so we can merge? I can't as I am an author to this PR as well.

Yes, just let me know when the dependencies are sorted out.

[VIPQualityPost]

I think the dependencies were all sorted out- just an issue with CI for now which might require bringing the PR in anyway so that the CI is not looking for old files.

[dl1com]

I think the dependencies were all sorted out- just an issue with CI for now which might require bringing the PR in anyway so that the CI is not looking for old files.

Yes...so I think we can merge this one for now to see if CI is working properly.
This enables @jpcornil-git to create the PR for the port of the new EOL code to 1.0 on the latest code.
So @t0mpr1c3, feel free to review/merge the PR.

[VIPQualityPost]

Are you sure we should merge to dev? I thought we don't want to do any ESP stuff until after 1.0 release. I agree we need a place to work on the refactor though. Maybe we can have a post-1.0 branch?

[dl1com]

Are you sure we should merge to dev? I thought we don't want to do any ESP stuff until after 1.0 release. I agree we need a place to work on the refactor though. Maybe we can have a post-1.0 branch?

Thanks for pointing that out.
Then I propose to just close this PR without merging and use this ayab-esp32 branch for this purpose.

[VIPQualityPost]

Agreed, let's just keep like that for now.