Bumps [geekyeggo/delete-artifact](https://github.com/geekyeggo/delete-artifact) from 1 to 2.
- [Release notes](https://github.com/geekyeggo/delete-artifact/releases)
- [Commits](GeekyEggo/delete-artifact@v1...v2)

---
updated-dependencies:
- dependency-name: geekyeggo/delete-artifact
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>

…go/delete-artifact-2

Bump geekyeggo/delete-artifact from 1 to 2

Bumps [carlosperate/download-file-action](https://github.com/carlosperate/download-file-action) from 1 to 2.
- [Release notes](https://github.com/carlosperate/download-file-action/releases)
- [Commits](carlosperate/download-file-action@v1...v2)

---
updated-dependencies:
- dependency-name: carlosperate/download-file-action
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>

…erate/download-file-action-2

Bump carlosperate/download-file-action from 1 to 2

Corrected Comment in AnalogInput.ino

Bumps [actions/checkout](https://github.com/actions/checkout) from 3 to 4.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](actions/checkout@v3...v4)

---
updated-dependencies:
- dependency-name: actions/checkout
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>

…/checkout-4

Bump actions/checkout from 3 to 4

The repository infrastructure includes a GitHub Actions workflow that compiles the examples for significant official
Arduino boards. This provides a automated "smoke test" to easily get some basic validation of the sketches.

Since the time the workflow was created, several new official boards have been released. Some of these boards are
significantly different from the boards the workflow was compiling the examples for, which meant the workflow was not
providing adequate coverage for the new boards.

The workflow is hereby configured to also compile the examples for the significant new boards.

The "ArduinoISP" example allows the user to define arbitrary pins for use as the signal pins on the programmer board.
This is done via a set of macros.

Previously, very generic names were used for these macros. This resulted in a name collision. The core for the Renesas
boards also defines macros of the same name. Despite what the names might lead us to believe, the values of these macros
in the core do not match the Arduino pin numbers of the SPI bus. The result was that, with the default configuration of
the sketch where the USE_OLD_STYLE_WIRING macro is not defined, the sketch uses the values of the macros defined by the
core as the SPI signal pins instead of the standard SPI signal pins as the user would expect when the sketch is running
on an UNO R4 Minima, UNO R4 WiFi, or Portenta C33 board. This causes operations using the programmer to fail with an
error like:

avrdude: stk500_recv(): programmer is not responding avrdude: stk500_getsync() attempt 1 of 10: not in sync: resp=0x03
[...]

The name collision is avoided by adding a "namespace" prefix to the macro names.

Use distinctive names for SPI pin macros to avoid collisions