* fix: Modify error message
* refact: Rename keys for consistency
* fix: Use scope_id in boundary_scope
The examples for the boundary_scope data source suggest to use `parent_scope_id`, but the provider is actually expecting `scope_id`.
* feat: add storage bucket resource
- Create a new resource for storage bucket
- Add examples and docs for how to use new resource
- Tests added but they do not run on purpose and have not been validated yet because we cannot run tests for enterprise features yet. That will be addressed separately
## Considerations
- Even though only AWS can be supported today, still added the `pluginID` & `pluginName` fields so it's easy to extend once other plugin types are supported
- There is some logic around handling secrets sent to Boundary and validating secret HMAC changes that exist from `boundary_host_catalog_plugin` that was introduced in [PR-159](https://github.com/hashicorp/terraform-provider-boundary/pull/159). Used the same logic we've been using for that
* Begin API updating
* Update scope and user providers
* Update group resource
* Update to TF plugin SDK v2
* Finish recovery KMS workflow
This also modifies groups tests to use it. It's easy to verify from the
controller output that it's being used since it causes warnings to be
printed.
* Finish porting group resource to proposed new paradigm
* Minor cleanup
* Allow specifying a particular token for auth
* base_url -> addr
* Add test using token
* Add set calls to Update
* Update SDK
* Update SDK
* Update user and scope
* Half of host catalog and some consolidation
* Finish host catalog
* Add host resource
* Add host set resource
* Update targets
* Some updates to newer API
* Start updating to response map standards
* Finish updating already ported resources to new paradigm
* Finish existing resource porting
* Update target to exercise default port
* Adapt target to using json.Number
* Add auth method and account resources