Create opbeans_user/role with write/read access for the opbeans-python

[v1v]

What does this PR do?

• Create opbeans role and opbeans_user with write/read access in Elasticsearch
• Default password: changeme
• Create OPBEANS_USER and OPBEANS_PASS environment variables.
• Expose those env variables for the opbeans-python container

Related issues

Closes #1032

Test

UI

$ hub pr checkout 1063
$ scripts/compose.py start master --with-opbeans-python
$ docker exec -ti localtesting_latest_opbeans-python env | grep OPBEANS
OPBEANS_USER=opbeans_user
OPBEANS_PASS=changeme
OPBEANS_SERVER_URL=http://opbeans-python:3000
OPBEANS_DT_PROBABILITY=0.50
OPBEANS_SERVICES=opbeans-python

[v1v]

Theoritically this hash is similar to the apm_server_user, so it should match changeme ideally.

I'm just guessing here

[apmmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Build Cause: Started by timer

• Start Time: 2021-02-22T04:00:00.694+0000

• Duration: 40 min 45 sec

• Commit: 7e32ef8

Test stats 🧪

Test	Results
Failed	0
Passed	488
Skipped	1
Total	489

Trends 🧪

[kuisathaverat]

Do we need the same user in the clusters?

[beniwohli]

@kuisathaverat we'll use those credentials to make some ES queries from the opbeans-python app, so if there is an opbeans-python instance that interacts with the clusters, we'd need it there too

[v1v]

I'll add them now