Wrap user-facing strings for internalization

[nung22]

Description

Updates user-facing strings in the Search Relevance plugin to be consistent with OpenSearch Dashboards guidelines. Strings are now wrapped and compatible with the default message extraction tool.

Issues Resolved

Closes #330

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.

[nung22]

I have only updated user-facing strings in flyout.tsx as of now. If the format of the FormattedMessage components (specifically naming convention for the id attribute) is satisfactory, I can proceed with the rest of the files.

[codecov]

Codecov Report

Merging #334 (a77bfa7) into main (966aed5) will decrease coverage by 4.64%.
Report is 1 commits behind head on main.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #334      +/-   ##
==========================================
- Coverage   87.08%   82.44%   -4.64%     
==========================================
  Files          16       32      +16     
  Lines         209      393     +184     
  Branches       43       77      +34     
==========================================
+ Hits          182      324     +142     
- Misses         26       49      +23     
- Partials        1       20      +19     

Flag	Coverage Δ
dashboards-search-relevance	82.44% <0.00%> (-4.64%)	⬇️

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

Files	Coverage Δ
public/components/common/header.tsx	100.00% <ø> (ø)
...re/search_result/result_components/result_grid.tsx	84.61% <ø> (-6.30%)	⬇️
...are/search_result/search_components/search_bar.tsx	66.66% <ø> (-8.34%)	⬇️
public/components/common/flyout.tsx	50.00% <0.00%> (-33.34%)	⬇️

... and 23 files with indirect coverage changes

[sejli]

Is it possible to wrap this entire in a single FormattedMessage block? May need to use brackets {} for the sub-components for formatting, like strong.

[nung22]

Thanks for the suggestion! I made changes to consolidate some of the FormattedMessage blocks.

[sejli]

Looks good so far! Could we see if we can wrap the entire string in FormattedMessage as per my comment? May be a little more readable. String IDs look good too, @joshuarrrr could you verify if this is a good starting place for wrapping in FormattedMessage?

Thanks for picking this up, this is great!