Cleanup AI-64

See merge request docs/docs.beagleboard.io!72

(cherry picked from commit 48521166)

e022461d Merge branch 'main' of git.beagleboard.org:docs/docs.beagleboard.io
e7d360ac Merge branch 'main' of git.beagleboard.org:jkridner/docs.beagleboard.io
8f6f1a8f Revert "Cleanup AI-64"
c41268e4 Add graphviz and move beagleconnect project
f0f934bd Try graphviz
aff59e88 Update BeagleV-Ahead license terms
c45bf163 Merge branch 'main' of git.beagleboard.org:docs/docs.beagleboard.io
db4f289a update librobotcontrol
be4e612c Clean-up board landing pages
c8e50111 projects: fix paths
b9e26d3a Merge branch 'main' of git.beagleboard.org:lorforlinux/docs.beagleboard.io
7912e911 Redo the introduction
bb0ccb64 Complete beagle101 move
dc8628f0 beagle101: fix toc
4f5fa485 Restore getting-started to the ToC
66717a6f beagleconnect: fix image path
db54f941 beagleconnect: adjust headings
ec3e8345 Update BVF support details
d67ae0d6 beagleconnect: add image fo...

This reverts merge request !71

Cleanup AI-64

See merge request !72

E3 was duplicated, replaced it correctly with E1

James Anderson sourced most of this doc based on a fork of the
BeagleBone Black or BeagleBone AI documentation:

See https://git.beagleboard.org/beagleboard/beaglebone-ai-64/-/commit/7440473917c08fb9bebc9dbeddc33b648b55762e#3086192f306e92a8bc70c5bbb05a122f1b464ad4_0_18

Adding consistent folder names for all baords.

* The USB branding is not consistent. Please take a read of the spec
  rather than random websites to provide more consistent terminology.
* The point of client-side cables is the
  single-cable-development-experience. It should be consistently
  highlighted.
* There is no "BeagleBone-X15". BeagleBoard and BeagleBone are not
  interchangable terms.
* For BeagleV-Ahead, it is important to note it is a type-AB receptacle
  because it can act as both a host and client at super-speed. This is
  the reason we put on the somewhat rare micro-AB connector--we want
  people to be able to use it both ways without violating
  specifications or requiring extensive software configuration.

cc @lorforlinux

Actually, all "BeagleBoard" boards are ARM, but not all Beagles. We need
to find better encapsulating terms. Specifically, this page only
addresses "BeagleBoard" boards, like BeagleBoard, BeagleBoard-xM, and
BeagleBoard-X15, not BeaglePlay, BeagleBone, BeagleConnect or BeagleV boards.

We've started using the term "Beagles" to refer to the entirety of the
product line.

BeagleBoard is meant to be embedded single board computers that are
low-power and small-size. Both xM and X15 added more upon this base.
They are all ARM+DSP based boards.

BeagleBone is meant to have the cape headers for embedded prototyping.
Originally, BeagleBone stood for "the bare-bones BeagleBoard" where less
was integrated onto the board and more header pins were available to
make it more optimized for embedded systems. We also dropped the DSP
from the original BeagleBoard. AI and AI-64 bring back the DSP for
performing AI tasks.

BeaglePlay is meant to be an easier-to-use computer with s...