Provide a name input field for saving tree tag selection locally (privately) or globally (publicly)

[bgirardot]

Right now if I do a set collection of features to export and then save them either locally or globally, they are all named Custom HDM Preset, even ones based on the OSM Data Model are called Custom HDM Preset

When selecting to save them locally or globally, there should be an input field to give them a name so they are not all named the same thing.

[bjohare]

Rather than adding another input field to the create export form, I've updated the Preset task to use the Export Name as the name for the preset and the filename is now set to 'job_name_preset.xml'

[bgirardot]

I'll leave this up to you as this is for sure an improvement, but I think naming it might be better from a resuse stand point.

That way I can name the selections as what they are (hospitals_heliports for example) instead of the name of the job, boma_south_sudan_presents, which doesn't help others or myself know what the preset file will include.

[bjohare]

Going to leave this for now. Have marked it as feature request for future development.

[bdon]

New feature selection form has name and description fields.