…n't existed (#2056)

#### Summary
The url for plugins doesn't existed(https://www.cloudquery.io/plugins)
and shows 404.

### Changes
I update the links from `https://www.cloudquery.io/plugins` to
`https://www.cloudquery.io/docs/plugins/source`

Adds migration guides for v1 plugins. Guides added in this PR:
-
[AWS](https://github.com/cloudquery/cloudquery/blob/migration-guides/plugins/source/aws/docs/v1-migration.md)
(Updated)
-
[Azure](https://github.com/cloudquery/cloudquery/blob/migration-guides/plugins/source/azure/docs/v1-migration.md)
-
[Cloudflare](https://github.com/cloudquery/cloudquery/blob/migration-guides/plugins/source/cloudflare/docs/v1-migration.md)
-
[DigitalOcean](https://github.com/cloudquery/cloudquery/blob/migration-guides/plugins/source/digitalocean/docs/v1-migration.md)
-
[GCP](https://github.com/cloudquery/cloudquery/blob/migration-guides/plugins/source/gcp/docs/v1-migration.md)
-
[Github](https://github.com/cloudquery/cloudquery/blob/migration-guides/plugins/source/github/docs/v1-migration.md)
-
[Okta](https://github.com/cloudquery/cloudquery/blob/migration-guides/plugins/source/okta/docs/v1-migration.md)

Heroku was left out because it was never released pre-v1. K8s will be
added when it is ready, and terraform requires some changes to work
(will follow up later today).

Generating these requires a bit of manual setup, but for future
reference, the process I have locally right now can be replicated using
something like this:

```
git worktree add ../v0
git worktree add ../v1
cd ../v0 && git checkout ab65d1e # or any v0 commit
cd ../v1 && make build
cd ..
```

Then run this script from outside the git root:

```
plugins="aws gcp azure cloudflare digitalocean github okta" 

mkdir -p docs/tables-v0
mkdir -p docs/tables-v1
for p in $plugins
do
	echo "Generating migration guide for $p"
	cp -r v0/plugins/source/$p/docs/tables/* docs/tables-v0
	./v1/bin/$p doc docs/tables-v1
	./v1/bin/v1-migration -o cloudquery/plugins/source/$p/docs/v1-migration.md -v1 docs/tables-v0 -v2 docs/tables-v1
done
```

#### Summary

<!--
Explain what problem this PR addresses
-->

---

Adding a new test destination for CLI testing purposes. The new
destination plugin is basically a dev null.

Also, Im proposing/trying out a .yml per plugin ? maybe this way we can
take advantage of the built-in github

```
    paths:
      - "plugins/destination/test/**"
```

For destination plugins I think this is specifaclly important because
the workflows vary very much between each plugin as we need different
databases and so on.

I think for source plugin this will also start becoming a thing when we
introduce some smoke tests that will require credentials and so on.

🤖 I have created a release *beep* *boop*
---


##
[1.1.0](plugins-destination-test-v1.0.0...plugins-destination-test-v1.1.0)
(2022-09-26)


### Features

* **dest-test:** Add new test destination
([#2057](#2057))
([d2e1df2](d2e1df2))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Make `aws_redshift_cluster_parameter_groups` a separate resource so that we can have `aws_redshift_cluster_parameters` under it.

Fixes #1979

Updates the `destination-test` plugin latest version to v1.1.0

#### Summary

Currently, if your RDS instance is publicly accessible, it passes the check to verify that it's not. If it's not publicly accessible, it fails as a false negative.

This should be fixed to prevent a bad policy check.

Co-authored-by: Kemal Hadimli <disq@users.noreply.github.com>

<!-- 🎉 Thank you for making CloudQuery awesome by submitting a PR 🎉 -->

#### Summary

closes #1884

<!--
Explain what problem this PR addresses
-->

---

Use the following steps to ensure your PR is ready to be reviewed

- [ ] Read the [contribution guidelines](../blob/main/CONTRIBUTING.md)
🧑‍🎓
- [ ] Test locally on your own infrastructure
- [ ] Run `go fmt` to format your code 🖊
- [ ] Lint your changes via `golangci-lint run` 🚨 (install golangci-lint
[here](https://golangci-lint.run/usage/install/#local-installation))
- [ ] Update or add tests 🧪
- [ ] Ensure the status checks below are successful ✅

This PR got messed up in conflicts
#2043

Co-authored-by: Herman Schaaf <hermanschaaf@gmail.com>

🤖 I have created a release *beep* *boop*
---


##
[0.2.0](plugins-destination-postgresql-v0.1.0...plugins-destination-postgresql-v0.2.0)
(2022-09-26)


### Features

* Move to standalone postgresql plugin
([#2074](#2074))
([a0de6d3](a0de6d3))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

This PR was created by a scheduled workflow to sync endpoint changes

Updates the `destination-postgresql` plugin latest version to v0.2.0

🤖 I have created a release *beep* *boop*
---


##
[1.1.0-pre.0](cli-v1.0.0-pre.0...cli-v1.1.0-pre.0)
(2022-09-26)


### Features

* Move to standalone postgresql plugin
([#2074](#2074))
([a0de6d3](a0de6d3))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).