Parse db.statement attribute for database instrumentation

[AsakerMohd]

Description of changes:
When "db.operation" is not provided in span attributes, the "aws.remote.operation" will be UnknowRemoteOperation.
This PR updated the setRemoteServiceAndOperation function to parsing the "db.statement" attribute when "db.operation" is missing, and extract the valid "aws.remote.operation" (We setup a set of valid database related "aws.remote.operation" for security concern):

1. Add a json file configuration/dialect_keywords.json saving all the valid keywords. In this file, the sequence of key words matter -> The keyword with longer word length are placed towards the front of the list so it will be matched first.
2. We retrieve the first 27 characters from "db.statement" to avoid the case where very large statements, and use regular expression to match the keyword, it will match the beginning of the string. If the string's start does not conform to the regular expression, the match fails.
3. Add unit test for setRemoteServiceAndOperation performance where tested DB_STATEMENT is/is not present and is/is not valid.
4. Add unit test covering different "db.statement" cases:
   1. Only 1 valid keywords match
   2. More than 1 valid keywords match, we want to pick the longest match
   3. More than 1 valid keywords match, but the other keywords is not at the start of the SpanAttributes.DB_STATEMENT. We want to only pick start match
   4. No valid match
   5. Have valid but it is not at the start of SpanAttributes.DB_STATEMENT
   6. Have valid keywords, match the longest word
   7. Have valid keywords, match with first word
   8. Have valid keywords, match with upper case
   9. Have both "db.statement" and "db.operation" set and the former is returned
5. Add unit test for testing keywords sequence in json file:
   1. Confirm the keywords are sorted based on descending order of keywords character length
   2. Confirm maximum length of keywords is not longer than MAX_KEYWORD_LENGTH

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[srprash]

I'm wondering if it will be more performant to just have the sql keywords as a list constant defined in the AwsSpanProcessingUtil class than to bring in a new dependency to read it from a json file.
@bryan-aguilar @vasireddy99 Any thoughts on this?

Also, if we decide to use the jackson dependency, please adhere to the existing format in the file for consistency. for example: implementation("com.fasterxml.jackson.dataformat:jackson-dataformat-yaml:2.15.1").

[srprash]

Also, why are we using the jackson-dataformat-yaml which is a yaml parsing lib for reading the json format file? Seems confusing.

[AsakerMohd]

Updated the dependency. As for storing in file vs in class, I'm not sure that matters much since now it it will read the file only once when the class is first initialized/called and after that, the list is stored in memory anyway.

[srprash]

Ok. I'm fine with reading the keywords from the file for now.

[srprash]

The PR description doesn't correctly mention the actual java methods used in this PR. Please fix the description to be more accurate.

[codecov-commenter]

Codecov Report

Attention: 6 lines in your changes are missing coverage. Please review.

Comparison is base (09e6487) 85.71% compared to head (a9f867b) 53.28%.
Report is 238 commits behind head on main.

Files	Patch %	Lines
...vaagent/providers/AwsMetricAttributeGenerator.java	76.47%	1 Missing and 3 partials ⚠️
...try/javaagent/providers/AwsSpanProcessingUtil.java	83.33%	2 Missing ⚠️

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@              Coverage Diff              @@
##               main     #755       +/-   ##
=============================================
- Coverage     85.71%   53.28%   -32.44%     
- Complexity       19      316      +297     
=============================================
  Files             3       40       +37     
  Lines            49     1432     +1383     
  Branches          5      176      +171     
=============================================
+ Hits             42      763      +721     
- Misses            3      622      +619     
- Partials          4       47       +43     

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