Add availability help flyout

[eugenesk24]

Description

Add availability help flyout to availability configuration panel

Issues Resolved

[List any issues this PR will resolve]

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-commenter]

Codecov Report

Merging #734 (9a3e8cc) into main (291d17f) will decrease coverage by 0.06%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##               main     #734      +/-   ##
============================================
- Coverage     58.20%   58.13%   -0.07%     
  Complexity      291      291              
============================================
  Files           242      243       +1     
  Lines          7981     7990       +9     
  Branches       1631     1633       +2     
============================================
  Hits           4645     4645              
- Misses         3162     3171       +9     
  Partials        174      174              

Flag	Coverage Δ
dashboards-observability	52.54% <0.00%> (-0.09%)	⬇️
opensearch-observability	71.87% <ø> (ø)

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

Impacted Files	Coverage Δ
...nts/flyout_components/availability_info_flyout.tsx	0.00% <0.00%> (ø)
...tom_panels/panel_modules/panel_grid/panel_grid.tsx	72.00% <0.00%> (-1.47%)	⬇️
...nfig_panes/config_controls/config_availability.tsx	2.50% <0.00%> (-0.36%)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 291d17f...9a3e8cc. Read the comment docs.

[Naarcha-AWS]

One small note, but otherwise LGTM.

[Naarcha-AWS]

Switch second sentence on line 47 to, "You can use the PPL language to define arbitrary conditions on their logs to create a visualization over time."

[eugenesk24]

Should it be your logs?

[Naarcha-AWS]

Correct, good catch :D

[ps48]

You should try using padding/margin here.

[opensearch-trigger-bot]

The backport to 2.1 failed:

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

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.1 2.1
# Navigate to the new working tree
cd .worktrees/backport-2.1
# Create a new branch
git switch --create backport/backport-734-to-2.1
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 159fc217c38b0a2a139ec642800097011b759312
# Push it to GitHub
git push --set-upstream origin backport/backport-734-to-2.1
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.1

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