feat: Cache hooks per Flag Evaluation Type

[chrfwow]

Hooks are now stored in a map to allow efficient lookup of hooks supporting certain FlagValueTypes. This and other changes makes merging the hooks cheaper.

Related Issues

Part of #1718

Follow Up Tasks

Implement efficient Hook Storage in all providers (optional, but will speed things up)

[sonarqubecloud]

Quality Gate passed

Issues
19 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[chrfwow]

• Make sure the additions of default methods to interfaces is not a byte code incompatibility

[codecov]

Codecov Report

❌ Patch coverage is 94.73684% with 4 lines in your changes missing coverage. Please review.
✅ Project coverage is 93.39%. Comparing base (bd70a3a) to head (b5a443f).
⚠️ Report is 7 commits behind head on main.

Files with missing lines	Patch %	Lines
src/main/java/dev/openfeature/sdk/HookSupport.java	86.95%	0 Missing and 3 partials ⚠️
...ava/dev/openfeature/sdk/FlagEvaluationOptions.java	87.50%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##               main    #1734      +/-   ##
============================================
+ Coverage     92.47%   93.39%   +0.92%     
- Complexity      527      548      +21     
============================================
  Files            52       53       +1     
  Lines          1276     1333      +57     
  Branches        112      129      +17     
============================================
+ Hits           1180     1245      +65     
+ Misses           60       50      -10     
- Partials         36       38       +2     

Flag	Coverage Δ
unittests	93.39% <94.73%> (+0.92%)	⬆️

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

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[chrfwow]

Benchmark results:
(I ran AllocationBenchmark#main with the IntelliJ Profiler. This is not a proper JMH benchmark, so the values are not representative per evaluation, but should be helpful to compare both versions)

Baseline:
Duration: 5267 ms
Allocations: 16.834 GB
Flamegraph of allocations:

This PR:
Duration: 5023 ms (this is an insignificant change, the deviations on those tests are quite large)
Allocations: 14.224 GB
Flamegraph of allocations:

[aepfli]

i am torn a little bit and not 100% convinced, that this will make things easier. maybe we should think about v2 and rethink our hooksupport api overall.

But i also do not have big remarks to add

[aepfli]

I am not sure, the order of hooks is important, i know that you are now using other methods, to retrieve the needed hooks, but can this implementation now be a problem, because we are not keeping the order of the hooks. Now we merge multiple hook source after each other.

[aepfli]

[suggestion] seems like this block of code repeats itself, should this maybe be a static helper function?