Update dependencies and ensure consistency in both the main library and samples

[Avery-Dunn]

Whenever CVEs are found or we need a new feature we update dependencies. However, it's been brought to our attention that some dependencies haven't been updated in years, and the dependency versions used in our various samples are not consistent with each other or the main library.

These dependencies should be updated where possible (at least where there are no breaking changes), to maintain consistency and help identify potentially deprecated features.