[Fixes #62] Remove re-exports to avoid warnings promoted to errors

[michalfita]

Purpose

My rustc 1.72.0 started to spit warnings at me, and CI fails on workflows with disabled minimum compiler version to be used (as 1.63.0 seems to be unaffected).

Scope

• Easy fix: Remove reexports as I'm not a fan of them coming from C++ world prefer namespaces leaving import renames to the user.
• Add building with the latest compiler to catch errors that may break people with newer toolchain than MRV.
• Reduce the strain on CI and remove doubling jobs.

Alternative

The alternative is to rename types to be more peripheral type specific. I have feeling at the moment we have mixture of both simple names in namespaces and specifically named peripherals despite being in namespaces.

[michalfita]

I cannot remove #![deny(const_err)] at the moment as it comes from PACs generation. The problem will solve itself when #61 is merged.

[michalfita]

This looks good to me, although it feels like the CI is slowly growing more and more unruly and there should be a better way to do this.

We could extend the matrix but the Rust Version component, but I don't have will power ATM to do this, but it would keep jobs definition flatter. Raise an issue if you prefer that way, @martinmortsell, and in future we may address this - now I'm aiming at making a release with separated PACs.