Move common-utils from external repo into OpenSearch

[dblock]

Is your feature request related to a problem? Please describe.
Coming from opensearch-project/common-utils#114, move common-utils into OpenSearch.

[nknize]

👎 for 2.0.0 it won't be ready:

1. There is a lot of legacy code that should be removed before refactoring to core
2. There is kotlin code that we need to tie in w/ the build hooks
3. The Integration Tests are Disabled w/ a note "Enable this after integration with security plugin is done" So why aren't we just integrating the appropriate classes with the security plugin?
4. There is no bwc integration tests and that will take some time to work out in core.

👍 for a future release if targeting core makes sense. We might want to integrate with security first (or dissolve the implementations across other plugins) then integrate security with core rather than blindly integrate with core.

[lezzago]

Regarding the integration tests for common-utils. I believe it does not make sense to have any integration tests for the package since the only way to create one is for plugins that depend on the package to create integration tests to test different functionality such as ensuring the Alerting plugin can make calls to the Notification plugin through the data models available in the common-utils package.