Add A300 attachments to config/yaml/attachments section

[civerachb-cpr]

Add A300 attachments to the yaml documentation. Move other pages back 1 position so A300 is first

[aws-amplify-us-east-2]

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-404.dfy90wyu8dics.amplifyapp.com

[rhysfaultless-cpr]

• The centre Wi-Fi / Bluetooth antenna is missing
• RPSW-2642 noted two configurations. Are both both of these supported in software?
  • Arch with single centred antenna
  • add the cellular antenna, and 2 more Wi-Fi duck antennas

Will

[civerachb-cpr]

What shape is the centre antenna? I'm just using the STLs you exported for me which includes 2 cylindrical antennas in one + the single boxy cellular antenna in the other.

For practical purposes, the STL is only used for the visual representation; the collision body is an over-sized box collider that's big enough to encompass several duck antennas. If the number/placement of the antennas doesn't exactly match it will only affect the visual model, but won't have any impacts on the robot's actual performance.

Currently the software does not support the two different visualizations; the arch always includes the cellular antenna + the two cylindrical antennas as pictured in amp_sensor_arch.png. Because the collider is over-sized and covers the whole upper region of the arch it didn't seem worth the extra complexity to either break out the antennas as their own attachment that would need configuration, or to add extra parameters to the arch that would only affect the visualization.

[rhysfaultless-cpr]

The 3rd antenna is the same size as the other duck antennas.

The images on the documentation website can be used as reference:
https://docs.clearpathrobotics.com/docs_robots/solutions/husky_a300_amp/

[civerachb-cpr]

Replaced the image with a new one showing all 3 antennas now that the URDF has been updated in 2.6

[civerachb-cpr]

Rebased to latest development branch