[Enhancement] Set up release directories for each integration and setup latest tag for each integration release

[RyanL1997]

Description

Since in PR opensearch-project/dashboards-observability#1860 of dashboards observability we have pointed the sourceURL to the release page of catalog repo, it is necessary for us to set up a release directory under each integration's asset directory. By doing that, we don't have to change the URL link in dashboards observability's sourceURL each time once we are having a new releases. In addition, we should also apply the latest label for the latest release version in catalog repo, so that the sourceURL can always be pointed to the latest release URL.

[Swiddis]

In principle, since we have legacy releases available in the releases page, we should limit the integrations here to always be the latest ones and let version control handle the historic versioning. Long-term we may want a dedicated version browsing space (the catalog webpage?) to work from, but short-term it works. The bulk of the work I think could be done by making a build directory containing a large bundle of all the built-in integrations in one:

build
|- opensearch_catalog.ndjson

For better granular version control we could also just have the whole per-integration repository directory copied and make the build process separate. Better practice and all.