Develop new client based on the new ElasticSearch client

Refer to:

• this issue refering to http-aws-es
• this wrapper to make secured connection to ElasticSearch on AWS. Kinda similar to http-aws-es so the current logic shouldn't need too much refactoring
• new client

The biggest change for us is that the new client doesn't return anymore only the body of the response when using promises, but it now returns the same object for both callback and promise approach:

{
  body: object | boolean
  statusCode: number
  headers: object
  warnings: [string]
  meta: object
}

@Holger-Will for the auto publish the current action is not working because I am not collaborator for this package on npm (so my token doesn't have publish rights for it)

You can either:

• add me as collaborator
• generate a token on your side and replace the secret NPM_TOKEN on this repo and that should do the trick

When you did it just ping me so I can give it a shot again and see if it works! 👍

Add action to automate layer publishing

[email protected] requires a peer of elasticsearch@^15.0.0 but none is installed. You must install peer dependencies yourself.

we probably have to npm i -D elasticsearch to make it go away

Slowly move dependencies to new client. For now they are using 0.0.1 so should still run

@Holger-Will do you wanna publish this to NPM? (not sure if it's already there anymore)