docs: Update releasing instructions to include manual steps and language release links

Author: EspenAlbert

RELEASING.md

@@ -3,19 +3,26 @@
 
 ## Stable release
 
-Stable releases are managed by the [Release GitHub Action](https://github.com/mongodb/awscdk-resources-mongodbatlas/actions/workflows/release.yml). You can release a new CDK version by manually trigger the action.
+Stable releases are managed by the [Release GitHub Action](https://github.com/mongodb/awscdk-resources-mongodbatlas/actions/workflows/release.yml). You can release a new CDK version by manually trigger the action ([REMEMBER Manual Steps Below](#manual-steps)).
 
 ![Screenshot 2023-04-20 at 10 35 11](https://user-images.githubusercontent.com/5663078/233325734-0f469045-f91b-436c-8dd5-19d1e8f24c57.png)
 
+### Manual Steps
 After the action finishes successfully you have to manually release the Go package:
 - Go to the [Go repo](https://github.com/mongodb/awscdk-resources-mongodbatlas-go) and check that the latest commit happened now with the same release as in this repo, e.g. `chore(release): v3.0.0`.
 - Go to the [Go Repo release page](https://github.com/mongodb/awscdk-resources-mongodbatlas-go/releases).
 - Select the latest release that has to be the same as the one in this repo, e.g. `awscdkresourcemongodbatlas/v3.0.0`, name will be like `v3.0.0`, click "Generate release notes" and make sure "Set as latest release" is checked.
 
+Also, to ensure no silent errors, look for the specific `vX.Y.Z` language releases:
+- [Javascript](https://www.npmjs.com/package/awscdk-resources-mongodbatlas?activeTab=versions)
+- [Java](https://central.sonatype.com/artifact/org.mongodb/awscdk-resources-mongodbatlas/versions)
+- [Python](https://pypi.org/project/awscdk-resources-mongodbatlas/#history)
+- [Golang](https://github.com/mongodb/awscdk-resources-mongodbatlas-go/releases)
+- [Nuget](https://www.nuget.org/packages/MongoDB.AWSCDKResourcesMongoDBAtlas#versions-body-tab)
+
 ## Versioning
 The release version is determinated based on the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/#summary) in that release.
 
-
 ## Release troubleshooting
 If the Release Gitub Action fails, it can happen that the new version is published only to some repositories, 
 but the failing ones are still in the current version.