Co-authored-by: per1234 <accounts@perglass.com>

Links in comment update

The Arduino documentation uses the new CIPO/COPI terminology while the whole arduino core still uses the old MISO/MOSI. 
While I thought about changing everything in the arduino cores, this would break many old sketches so I figuered adding a hint is the way to go.
Also, only changing terminology in this sketch doesn't work for consistency reasons, eg. beginning in line 106.

Co-authored-by: per1234 <accounts@perglass.com>

ArduinoISP: Add hint MISO/MOSI -> CIPO/COPI

As the primary maintainer of the project infrastructure, it is the responsibility of GitHub user per1234 to review and
merge the pull requests automatically submitted by Dependabot for bumps of outdated project dependencies.

Configuring Dependabot to automatically set the pull request assignment will slightly streamline that process.

The Dependabot service is used to keep the project dependencies updated.

Thanks to the project's high quality validation infrastructure, the human effort required to complete a trivial version
bump is minimal. However, some bumps may introduce breaking changes that would require a significant amount of effort to
accommodate, or are blocked by external tasks. In this case, the Dependabot pull request can't be merged, but should be
left open to track the need to perform the bump when it is feasible. This means that it should be expected that there
will be regularly be a small number of Dependabot pull requests left open in the repository over long periods of time.
The automated system is here to assist the human project maintainers, not as a tyrannical overlord, so this is the
system working exactly as intended.

By default, Dependabot is configured to stop submitting pull requests if it already has five open pull requests. This
means that if it happens that the accumulation of intentionally on-hold pull requests reaches that number, the project
stops receiving the easily handled trivial update PRs. This is very harmful because it results in the completely
unnecessary use of outdated dependencies, and unnecessary challenging large bumps when pull requests start being
submitted once more after the backlog is cleared.

The harmful default configuration is hereby overridden by configuring the maximum open pull request limit at 100. This
value was chosen as an arbitrary large number simply to functionally disable the limiting, rather than from any
expectation that the actual number of open PRs can ever reach that count.

Don't limit number of open Dependabot pull requests

The "Knock" sketch polls the voltage output from a piezo disc to detect the vibrations associated with a knock.

The duration of vibrations from a single knock is likely to significantly exceed the unchecked polling interval. This
would result in a single knock producing multiple detections, and thus multiple prints to Serial. In order to avoid
this, a "debouncing" delay was added to the sketch.

Previously the delay was positioned in the outer scope of the `loop` function, which caused it to always affect the
polling interval. This caused the sketch to miss the detection of knocks that produced vibrations that only occurred
during that unnecessary delay. The problem is fixed by moving the delay inside the knock detection conditional block, so
that debouncing is only done when actually needed.

Only delay after serial output in "Knock"

Bumps [actions/upload-artifact](https://github.com/actions/upload-artifact) from 3 to 4.
- [Release notes](https://github.com/actions/upload-artifact/releases)
- [Commits](actions/upload-artifact@v3...v4)

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

Signed-off-by: dependabot[bot] <support@github.com>

Bumps [actions/download-artifact](https://github.com/actions/download-artifact) from 3 to 4.
- [Release notes](https://github.com/actions/download-artifact/releases)
- [Commits](actions/download-artifact@v3...v4)

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

Signed-off-by: dependabot[bot] <support@github.com>

Bumps [geekyeggo/delete-artifact](https://github.com/geekyeggo/delete-artifact) from 2 to 5.
- [Release notes](https://github.com/geekyeggo/delete-artifact/releases)
- [Changelog](https://github.com/GeekyEggo/delete-artifact/blob/main/CHANGELOG.md)
- [Commits](GeekyEggo/delete-artifact@v2...v5)

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

Signed-off-by: dependabot[bot] <support@github.com>

The "Sync Labels" GitHub Actions workflow is configured to allow the use of multiple shared label configuration files.
This is done by using a job matrix in the GitHub Actions workflow to download each of the files from the source
repository in a parallel GitHub Actions workflow job. A GitHub Actions workflow artifact was used to transfer the
generated files between sequential jobs in the workflow. The "actions/upload-artifact" and "actions/download-artifact"
actions are used for this purpose.

Previously, a single artifact was used for the transfer of all the shared label configuration files, with each of the
parallel jobs uploading its own generated files to that artifact. However, support for uploading multiple times to a
single artifact was dropped in version 4.0.0 of the "actions/upload-artifact" action. So it is now necessary to use a
dedicated artifact for each of the builds. These can be downloaded in aggregate by using the artifact name globbing and
merging features which were introduced in version 4.1.0 of the "actions/download-artifact" action.

…/upload-artifact-4

Bump actions/upload-artifact from 3 to 4

The sketches under the "10.StarterKit_BasicKit" folder are provided to accompany the Arduino Projects Book of the
Arduino Starter Kit. The Arduino Projects Book explains the code of these sketches and gives instructions for their
usage.

In addition to owners of the Arduino Starter Kit, other users might use these prominent sketches as learning references.
Those users won't have the context that would be provided by the Arduino Projects Book. For this reason, explanatory
comments have been added to these sketches.

The "p08_DigitalHourglass" is unique in that it is intentionally left incomplete. The Arduino Projects Book instructs
the user to add their own code to indicate the completion of the timer. It is important that this code be added, since
the incomplete code does not halt the LED control code at the end of the hour. If the incomplete code is used unchanged,
the LED control code will call `digitalWrite` on additional pins.

Previously, the comments in the sketch did not explain the incomplete nature of the sketch. Comments are hereby added to
explain this to users who don't have the context provided by the Arduino Projects Book.

Document incomplete nature of "p08_DigitalHourglass"