Use go:build tags for testing

[Jakob3xD]

Description

• add go:build tags to integ tests
• add options to makefile to select integ test
• use new make functions in workflows
  Followup PR for Add ISM Policy #524 (review)

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

All modified and coverable lines are covered by tests ✅

Project coverage is 66.99%. Comparing base (06a6dc8) to head (60708bd).
Report is 12 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #529      +/-   ##
==========================================
+ Coverage   57.29%   66.99%   +9.70%     
==========================================
  Files         315      376      +61     
  Lines        9823     8850     -973     
==========================================
+ Hits         5628     5929     +301     
+ Misses       2902     1599    -1303     
- Partials     1293     1322      +29     

Flag	Coverage Δ
integration	60.38% <ø> (+9.54%)	⬆️
unit	81.64% <ø> (+68.79%)	⬆️

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

see 250 files with indirect coverage changes

[dblock]

I like it!

Let's rename things to be more consistent.

OpenSeearch engine is called either "core" (that's how we refer to the repo) or "min" (that's the name of the distribution), so rename "base" to "core" or "min"?

Since we're testing multiple plugins let's call "plugin" "plugins"?

To avoid confusion between things like "integration", I think we should prefix plugin tags with "plugin", e.g. "plugin-security" and name plugins to match their actual name, so instead of "ism" let's call it "index-management".

[dblock]

Nice and clean.