fix(quickstart): elasticsearch-setup script fails on curl

[shirshanka]

PR #5887 caused a failure in the elasticsearch-setup script when insecure mode is not used, due to a sneaky bug.

curl -o /dev/null .. -s "$ELASTICSEARCH_INSECURE" "$ELASTICSEARCH_PROTOCOL://...." 

will result in:
curl -o /dev/null .. -s "" "http://localhost:9002/..." 

which results in curl trying to hit 2 urls... the first being an empty string. 

This PR fixes this by re-attaching the ELASTICSEARCH_INSECURE flag to the beginning of the url
"${ELASTICSEARCH_INSECURE}$ELASTICSEARCH_PROTOCOL://..."

a better fix would probably be to refactor the CURL_OPTS into a separate variable that adds the -k flag if needed.

Would like to get this PR in first to limit the refactor.

Tested locally by building the docker image and verifying that a clean quickstart now completes cleanly with es-indexes set up correctly.

Checklist

• The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
• Links to related issues (if applicable)
• Tests for the changes have been added/updated (if applicable)
• Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
• For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

[jjoyce0510]

Just curious -- Why is all of the new __STATUS stuff required?

[shirshanka]

found the real problem... fixed up the PR

[WarFox]

2022/09/27 11:32:26 Waiting for: http://elasticsearch-master:9200
2022/09/27 11:32:26 Received 200 from http://elasticsearch-master:9200
Going to use protocol: http
Going to use default elastic headers
Create datahub_usage_event if needed against Elasticsearch at elasticsearch-master:9200
Going to use index prefix::
curl: option -k http://elasticsearch-master:9200/_ilm/policy/datahub_usage_event_policy: is unknown
curl: try 'curl --help' or 'curl --manual' for more information
Policy GET response code is
/create-indices.sh: line 41: [: -eq: unary operator expected
/create-indices.sh: line 45: [: -eq: unary operator expected
/create-indices.sh: line 47: [: -eq: unary operator expected
Got response code  while creating policy so exiting.
2022/09/27 11:32:26 Command exited with error: exit status 1

We're getting this failure when upgrading to linkedin/datahub-elasticsearch-setup:v0.8.45 using helm chart 0.2.106

Looks like curl still gets -k option on our installation, it's weird