Split off ES section into a separate add_es_data.sh script (Was: Update add_data.sh script to allow running Postgis and ES sections independently)

[arashmalekz]

We sometimes use Postgis database dumps to populate the database and don't need to run the code in add_data.sh to create Postgis data. It would be useful to have a flag in the .env file to select whether Postgis or ES should be populated or both.

[anthonyfok]

Hi Arash! Thanks for bringing this up!
This happens to be something related, i.e. trying to resume add_data.sh interruption due to an error or manual abort, or to do some kind of "unit testing", etc., by moving each "section" into individual functions, with build stamp, etc.
And, sorry for the delay! I'll be working on this issue during this Sprint 35. Cheers!

[anthonyfok]

Hey @drotheram and @arashmalekz, I'm going to reuse this Issue into splitting off ES sections of add_data.sh into add_es_data.sh, and use this as an excuse for me to split off the helper functions to another separate file.
(Sorry for being dormant for so long!)

[arashmalekz]

Great, that split sounds good with me!