Fix integration labeling to identify S3 integrations

[Swiddis]

Description

The last of this particular round of bug bashing: depends on #1155 and #1156, this PR swaps out the labels to help find useful integrations faster. In particular it adds a Flint S3 label to identify flint-compatible integrations.

Issues Resolved

N/A

Check List

• New functionality includes testing.
  • All tests pass, including unit test, integration test and doctest
• New functionality has been documented.
  • New functionality has javadoc added
  • New functionality has user manual doc added
• Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[codecov]

Codecov Report

Merging #1157 (f9a397d) into main (3aefc10) will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1157   +/-   ##
=======================================
  Coverage   44.22%   44.23%           
=======================================
  Files         329      329           
  Lines       19552    19545    -7     
  Branches     4723     4722    -1     
=======================================
- Hits         8647     8645    -2     
+ Misses      10337    10332    -5     
  Partials      568      568           

Flag	Coverage Δ
dashboards-observability	44.23% <ø> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 2 files with indirect coverage changes

[opensearch-trigger-bot]

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/dashboards-observability/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/dashboards-observability/backport-2.x
# Create a new branch
git switch --create backport/backport-1157-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 562c3e044c8a0d2cfc4e9029d37b9b73a0d4cc92
# Push it to GitHub
git push --set-upstream origin backport/backport-1157-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/dashboards-observability/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-1157-to-2.x.

[opensearch-trigger-bot]

The backport to 2.11 failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/dashboards-observability/backport-2.11 2.11
# Navigate to the new working tree
pushd ../.worktrees/dashboards-observability/backport-2.11
# Create a new branch
git switch --create backport/backport-1157-to-2.11
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 562c3e044c8a0d2cfc4e9029d37b9b73a0d4cc92
# Push it to GitHub
git push --set-upstream origin backport/backport-1157-to-2.11
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/dashboards-observability/backport-2.11

Then, create a pull request where the base branch is 2.11 and the compare/head branch is backport/backport-1157-to-2.11.