What: This change moves project-level bucket metadata encryption information to the volatile section, because it is unlikely to remain in future releases
Why: Ultimately, the web user interface will allow bucket management (creation, removal, etc), but not object management as that requires an encryption key for sure and we don't want to have users give the satellite their encryption keys.
At a high level, a (*Project) type should map to all of the things you can do inside the web user interface within a project, which by necessity cannot have an encryption key. So, we really don't want an encryption key in the non-volatile section of this library.
* Merge in upstream
* Some initial wireup
* Added common.go file, more misc. work
* WIP adding identity in
* Get FullIdentity combined into Uplink
* Structure libuplink a little better
* Update some types and add some comments
* WIP uplink stuff
* Get uplink types and configs figured out
* add initial setup for tests, happy path is working
* Remove dependency from miniogw
* Adds miniogw code and wires it up correctly
* WIP working on getting test suite setup
* Uplink client now returns successfully and passes some initial happy path tets
* WIP trying to get v2 draft ready
* WIP
* WIP wiring up bucket methods and adjusting to some review feedback
* Getting closer to v2 libuplink draft
* CreateBucket now works and has tests to prove it
* Bucket tests are passing now
* removing some code
* Updates error handling and linter fixes
* Removes main_test
* Uploads and downloads are now working
* Rename BucketOpts to Encryption
* updates
* added test file back to git that was being ignored for some reason
* more test conditions
* changes Checksum in ObjectMeta struct to be type []byte
* linter fix
* Updates how encryption is passed through to bucket opts
* Updates encryption handling at bucket and access level
* Fixes imports
* Updates per code review
