Support EYESPI default pins on QtPy / other boards

Adding an E-Ink with EYESPI connector to a QTPY, you use an EYESPI B.F.F, and have to lookup the pins on the EYESPI BFF learn guide, which we don't link to in wippersnapper. It's not complex, but for a beginner there's a few complexities, you mainly copy the pinout mentioned, inferring DC means data command, and that there's no Busy pin.

In an ideal world, we could let the user add the EYESPI BFF as a component or something, bridging the missing connectivity/information (and linking an appropriate learn guide).
More likely we could get the new component dialog for 2.9" eink to match to the qtpy's default pins for displays.
So we'd need to define some extra autoMatch strings in the component def, like the qtypy's A2 board definition entry would get an extra match string of "ECS" for e-ink chip select for example (matching the autoMatch string for e-inks chip select string in io-rails or the 2.9" eink components definition entry for that chip select pin).

This is a long term goal as we have very few eyespi displays, but as revisions are done most will be incorporated.
We can also add a wippersnapper page to some of the more generic component learn guide pages, like https://learn.adafruit.com/monochrome-oled-breakouts and the QTPY BFF product learn guide, which will help.

Start by locating the QtPy A2 board definition, the component definitions, and the io-rails autoMatch entries mentioned in the issue. Compare the QtPy default display pins with the 2.9" E-Ink definitions and determine whether matching or a new EYESPI component is the intended path. Done means the relevant E-Ink component uses the QtPy defaults and the appropriate learn-guide links are available.

Written by the indexing model from the issue text.