Change GlobUtil, IncludeExcludePredicate to use case sensitive matching consistently

[jack-berg]

Resolves #8137.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.29%. Comparing base (bc73a5e) to head (5cecf3c).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##               main    #8152   +/-   ##
=========================================
  Coverage     90.29%   90.29%           
+ Complexity     7650     7649    -1     
=========================================
  Files           843      843           
  Lines         23059    23059           
  Branches       2309     2309           
=========================================
+ Hits          20821    20822    +1     
+ Misses         1519     1518    -1     
  Partials        719      719           

☔ 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.

[breedx-splk]

looks good to me

[trask]

do we need also to include

opentelemetry-java/sdk/common/src/main/java/io/opentelemetry/sdk/common/internal/GlobUtil.java

Lines 101 to 102 in bc73a5e

	// Exact match, ignoring case
	return globPattern.equalsIgnoreCase(s);

[jack-berg]

do we need also to include

Pushed a commit to extend to GlobUtil, but this definitely widens the scope of impact, since metric view name selection is impacted.

I still characterize this as a bug fix, since as GlobUtilTest updates show, the pattern matching portion of was still case sensitive despite the exact match being case insensitive. One way or the other, we have to make it consistent, and I see no language in the spec to suggest that view metric name matching, glob patterns, or matching in general should be case insensitive.

[trask]

characterize this as a bug fix

👍