And some logging messages have had their level changed.

Reflects move of untracked files to /storage/app/EWS/<region>/Resources/
for archiving there.

The second plot is changed to cover the whole simulated period, from
the start of the season to the end of the forecast period.
Epi plot titles have also been reworded.

The email config is required to set up the logging before any other
tasks are done in order to maximise coverage. It is expected that the
location of the required config file is defined in run_Processor.sh,
or exported to local environment before calling Processor.py.

The ssh commands now do not check new server identities. This prevents a
user prompt on first-time use, which otherwise inhibits Amazon Web
Server instances.

Adding TempOnly env.suit. runs.

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

All non-git-tracked files required to run the operational aspects of the
early warning system are now stored in a project specific directory
called Resources/.
This should ease archiving and redeployment.

EnvSuit pipeline update, to handle cleaning, job generation, and multiprocessing in a more direct way.

There are a number of supporting resources for running the EWS pipeline,
including shapefiles, preprocessed files, server credentials and some
config files, all of which are not git controlled. The plan is to consolidate them in a dedicated directory for each project, called Resources. This commit applies that changes for the Advisory component of the EWS. It has been tested for both Ethiopia and SouthAsia.

* configurable timespan can now state a fixed date in the past with a
  string <YYYYMMDD>.

* Epi plotting now generates two figures, one for integrated epi risk
  over past dates (from start of CalculationSpanDays until
   --start-date date), and a second for
  integrated epi risk over future dates (from date of --start-date
  until  end of configured CalculationSpanDays)