chore: Tidy imports

Can be called with command line flag '-p Scraper'.
To use, the config file requires the following minimal entry (with
URL for South Asia):
    "Scraper" : {
	    "ProcessPreJob" : "do_nothing_return_true",
        "ProcessInJob" : "process_in_job_media_scraper",
        "ProcessEWSPlotting" : "do_nothing",
        "seasonStartString" : "20220101",
        "URL" : "https://arrcc-viewer.onrender.com/assets/sample_data/data.zip"
    },

1) There is now a python alternative to the R-based wheat-source-
generation, called source_gen. The functionality to call source_gen
has been added (see ProcessorSurveys.pyL939 and L1032-1040), but not
yet switched on while we await testing of
output at the Met Office.

2) ProcessorComponents was huge (2100 lines!) and the structure was
not apparent. Each component's supporting functions are now in a
separate directory. There is also a ProcessorServer.py relating to
file down/up-loads. ProcessorComponents is now essentially a directory
 to import all the functions. This might inspire a more systematic
 (object-oriented?) structure for each component within coordinator
 in the future.

reading NAME.nc files rather than NAME.txt files (#19)

reverting code to run in the standard way (running with overwrite as false, etc). Removing redundant code from EnvSuitPipeline.py

There are now three different functions used to download surveys from
three different server types: ODK, kobotoolbox and WRSIS. All three
functions can use past downloads if there is no connection currently, but
they have different hard-coded settings. This fix makes them
consistent and configurable with the config parameter
['Survey']['AcceptableDowntimeDays'].

import and shell script changes to use new plotting and met_extractor (now met_processing) package structures

An input argument config['Epidemiology']['Deposition']['VariableNames']
is expected as a list, so that a different variable name can be loaded
 for each listed disease. The list parsing has a bug, and is picked up
only now because the config file now provides a list of variable names.

The preparation of deposition data is quite long winded so it is moved
a standalone function.

Now that the epi model has been evaluated, parameterised, and
EWS-plotting run config have all been agreed.

And some logging messages have had their level changed.

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 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.

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)

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.

Add WRSIS as a possible survey option. (New functions: WRSIS http request, json normalization, nested data flattening, and incident caltegorization)

To match EWS-advisory-builder commit 92edec8.