…so fix some bugs related to JSON parsing

…corp#133

* Tidyup (hashicorp#142)

- Generate docs using latest tfplugindocs tool
- Update plugin SDK 
- Use go 1.18

* fix typo in docs

* Update Changelog

* update go-version

* v0.4.4

* Migrate Provider Releases from TeamCity to GitHub Actions

Internal RFC References:

* ENGSRV-035
* ENGSRV-064
* SEC-036
* SEC-061
* TF-279

_Please note: This process can be adjusted to suit your needs, but it will require changes to the workflow setup._

The initial release workflow submitted here is triggered by pushing a semantic version tag prepended with a `v` to the repository. For example:

```shell
git switch main # or your release branch
git pull
git tag v1.2.3
git push origin v1.2.3
```

The most important distinction from the TeamCity release process is that the repository must be fully prepared for the release, including the `CHANGELOG.md` file. Providers can decide the most appropriate process to manage the CHANGELOG or any release notes as part of this new process. This initial workflow will automatically grab contents from the top of the CHANGELOG through the previous release tag header line. [Example provider CHANGELOG](https://github.com/hashicorp/terraform-provider-tls/blob/156ae39c7e55ee8597f859a77ae2db739527376b/CHANGELOG.md) and its [GitHub Release description](https://github.com/hashicorp/terraform-provider-tls/releases/tag/v3.3.0).

Please reach out if you have questions.

* Onboard project to Releases API

* Update to include terraform registry manifest

Co-authored-by: Kyriakos Oikonomakos <[email protected]>
Co-authored-by: Kyriakos Oikonomakos <[email protected]>
Co-authored-by: tf-release-bot <[email protected]>
Co-authored-by: Brian Flad <[email protected]>
Co-authored-by: Jeanne Franco <[email protected]>
Co-authored-by: claire labry <[email protected]>

This reverts commit 5bfc51f.

merge main