[ZEPPELIN-6130] Write a Dockerfile for Elasticsearch interpreter image build

[ParkGyeongTae]

What is this PR for?

This PR adds a Dockerfile to build a elasticsearch interpreter.

What type of PR is it?

Feature

Todos

• - README.md
• - Dockerfile
• - Dockerfile_elasticsearch

What is the Jira issue?

• https://issues.apache.org/jira/projects/ZEPPELIN/issues/ZEPPELIN-6130

How should this be tested?

• Build and run Elasticsearch with Docker

# Build
docker build -f ./elasticsearch/Dockerfile_elasticsearch -t elasticsearch .
# Run
docker run -d -p 9200:9200 -p 9300:9300 --name elasticsearch elasticsearch

• Build and run the Elasticsearch interpreter with Docker

# Build
docker build -f ./elasticsearch/Dockerfile -t elasticsearch-interpreter .
# Run
docker run \
--name elasticsearch-interpreter \
-p 8087:8087 \
-e INTERPRETER_EVENT_SERVER_PORT=${__YOUR_INTERPRETER_EVENT_SERVER_PORT__} \
elasticsearch-interpreter

• Edit interpreter.json

# Old
  "elasticsearch": {
      "...": "...",
      "option": {
        "remote": true,
        "port": -1,
        "perNote": "shared",
        "perUser": "shared",
        "isExistingProcess": false,
        "setPermission": false,
        "owners": [],
        "isUserImpersonate": false
      }
    }
# New
  "elasticsearch": {
      "...": "...",
      "option": {
        "remote": true,
        "host": "host.docker.internal",
        "port": ${__YOUR_INTERPRETER_EVENT_SERVER_PORT__},
        "perNote": "shared",
        "perUser": "shared",
        "isExistingProcess": true,
        "setPermission": false,
        "owners": [],
        "isUserImpersonate": false
      }
    }

• Verify that the shell interpreter container communicates with the zeppelin server.

Screenshots (if appropriate)

Questions:

• Does the license files need to update? Yes
• Is there breaking changes for older versions? No
• Does this needs documentation? Yes