Consider renaming the project to avoid confusion

[pavel-kirienko]

⚡ Feature Request

Please Describe The Problem To Be Solved

UAVCAN ceased to exist around March 2022, having been forked into two projects that share a common ancestry but are fundamentally different:

• DroneCAN, formerly UAVCAN v0, is aimed at consumer drones with simple centralized network architectures.
• Cyphal, formerly UAVCAN v1, is aimed at complex real-time high-integrity cyber-physical systems.

The current name might lead one to incorrectly assume that the library can be used with DroneCAN.

(Optional): Suggest A Solution

Rename it. At the technical level, there are no changes required as any valid UAVCAN/CAN v1 implementation is also a Cyphal/CAN implementation.

[aentinger]

If its urgent, PRs are accepted. Otherwise I'll get to it in the coming weeks.