Use arduino_ci for testing

[ianfixes]

Full disclosure: I'm the owner of the arduino_ci project, and this is not meant as an attempt to convince you to use it.

This was my own exercise to see what shortcomings might exist in my software (I found a few) and I'm sharing the results here. Until now I had been testing against libraries that did not already have a unit testing capability, which meant that I had no idea whether I was covering all of the features one might expect. AceButton has some well-developed testing processes, and so it was satisfying to me to see the passing build status on my branch (hopefully indicating that I've achieved some level of parity with AUnit).

Since you are also the maintainer of a build system for Arduino libraries, I would welcome your feedback (as candid as possible, positive or not) on these changes and the build logs themselves. Does it look sensible? Does it convey the information you want? Am I passing things that should fail? etc.

Summary of changes:

• Added 2 flavors of CI
  • one that's server-only (no local setup required)
  • one that mirrors the way you'd test locally (Gemfile, Gemfile.lock, and .ruby-version)
• Added the dependency on AceCommon to library.properties (my test script responds to this) and removed its script-based installation method
• moved tests/*/*.ino to test/*.cpp (my software expects to find them there) and switched over the test macros. This actually "just worked"!
• initialized the static const int member variables from the AceButton class
• Removed the Jenkinsfile (not having access to Jenkins, I wasn't sure it was worth trying to guess what the pipelines might do). The procedure in the Jenkinsfile was recreated in arduino_ci_test_runner.yml
• The custom library needed by the CapacitiveButton example is now installed by the install_dependencies.sh script in that directory. It's invoked by CUSTOM_INIT_SCRIPT in the GitHub-action-based workflow, and by manually calling it in the "test runner" workflow. If/when the necessary changes hit the released version of the CapacitiveButton library, the custom script can be replaced with an entry in library.properties.
• Commented out test(LadderButtonConfig, extractIndex) because it wasn't immediately clear to me how to fix that
• Removed all supporting files for Aunit, like Makefile

[bxparks]

Hi, Just to make sure that I understand the purpose of this PR, you are not actually requesting this to be merged into the AceButton code, right? Because I don't think I would ever merge this. So the purpose of this is to discuss the features and potential deficiencies of your arduino_ci framework. I would be willing to engage in some of that, but I don't think this PR is the right place for that discussion. Doing that here would generate spam for the subscribers of this project, most of which would be irrelevant to them.

Since you have forked AceButton, I think a better way would be for you to create a PR of this change into your fork, then add me as a reviewer of that PR, so that we take this discussion off of this project. Does that sound reasonable?

[ianfixes]

I don't think I would ever merge this

The reasoning behind this is precisely what I'm interested in learning. I hope we can focus on this in the PR discussion in my own branch https://github.com/ianfixes/AceButton/pull/1