crontab and ewsdev configs now refer to configs in project-specific
resources directories.

Will has been sending both netcdf and txt versions of NAME results for a while now.
When fully adopted and txt results are no longer sent, this has the
advantage of smaller data load on storage and transfer.
Here, the nc has been implemented for deposition only, since it is a
straightforward change.
The environmental suitability input (NAME met output) still needs to
be done.

The newly imported AdvisoryBuilder can be run separately, see
that project for more details.
Updated conda environment accordingly.

There is a fudge to iterate over diseases, which should be improved.

This configuration works with EWS-EpiModel git commit 631e3520. This can handle multiple diseases but only one region. Output directories are <job-directory>/<region>/<disease>/<output>

For now, one set for production, called 'live', and a second for development 'ewsdev'. Advise any clone of the repo creates its own set of these config files. This resolves the issue of having local uncommitted modifications to config files.

This should only apply to the operational copy of the EWS-Coordinator. If you want to run a separate copy for any reason, make these changes to point to your separate workspace. The git ignored files still need pointing to, but they don't need to be duplicated. Your local version of these changes can be stashed while pushing and pulling to/from the master branch.

In operational version, this is needed for survey results. The way this is implemented, it can be configured for any other component too.

Updating Env Suit v2.0 calculation. Copied from operational EnvProcessor.py in master branch. Not tested for this commit.

Initial commit. Currently only working for Nepal deposition and (partially for) Ethiopia environment v2.0