User can save a map to Azure storage

[mikefab]

What type of data to be saved?

Maps - kepler exports maps into a file called config.json. It has three nodes:

• datasets: an array of datasets
• config: the layer configurations which contain dataset names (dataId to be exact, which references the id value inside the datasets node. See Kepler.gl docs here and here).
• info: metadata about the file itself.

Where should the data be stored?

UNICEF uses Azure, so many static files are in Azure blob or file storage. Here is an npm module to interact with Azure.

What functionality should the feature have?

When a user logs in to create a map, a function should check to see if they have a storage folder already in Azure storage. If not, one should be created with their username. The user should be able to create a visualization and then name and save the map to this folder when it is completed.

As a bonus, create an autosave feature that saves an untitled map upon creation and periodically throughout (every x seconds or minutes, for example) and/or create an alert that would remind user to save before closing out the browser window.

Test datasets and sample maps will be made available on Azure storage or via a drive

[cpitman]

Depends on #8