Rename lib/cloud/aws/config to lib/cloud/awsconfig

[GavinFrazar]

This is a package we recently added as part of an AWS SDK v1->v2 migration effort, but I think the package name "config" is just too generic.
There are already several "config" package in our repo and in our dependencies.

The reason I singled out this package for renaming is because I want to use it in more and more packages as I migrate them to AWS SDK v2, and I kept having to rename the import.
I'd like to just rename it now while there's a tiny number of packages that depend on this package.

https://go.dev/blog/package-names#package-names

The name of the package is a critical piece of its design. Work to eliminate meaningless package names from your projects.

Don’t use a single package for all your APIs. Many well-intentioned programmers put all the interfaces exposed by their program into a single package named api, types, or interfaces, thinking it makes it easier to find the entry points to their code base. This is a mistake. Such packages suffer from the same problems as those named util or common, growing without bound, providing no guidance to users, accumulating dependencies, and colliding with other imports. Break them up, perhaps using directories to separate public packages from implementation.

Avoid unnecessary package name collisions. While packages in different directories may have the same name, packages that are frequently used together should have distinct names. This reduces confusion and the need for local renaming in client code. For the same reason, avoid using the same name as popular standard packages like io or http.