Configurable data extracts via YAML config, so user can define which linear feature type to split on

[Sujanadh]

Is your feature request related to a problem? Please describe.
Currently, we are filtering data extracts in the fmtm-splitter algorithm by hardcoding tags, for example, highways (residential, pedestrian, track), which sometimes creates irrelevant splits.

Describe the solution you'd like
This filtering should be done when extracting data from OSM instead of filtering after the data is extracted.

Describe alternatives you've considered
An alternative approach can be creating a dynamic yaml config file like we do for dynamic xls form edit in fmtm so that users can filter tags themselves based on their desired splitted task response. This can be done on a platform like FMTM so that the algorithm doesn't have to rely on the hardcoded filters.

Additional context
Add any other context or screenshots about the feature request here.

[spwoodcock]

For context: before splitting the provided features, we first download a data extract of linear features (major roads, rivers, etc). This is used to divide the features by. By default we use major highways, waterways, aeroways, railways.

It's a good idea to allow the type of selected linear features to be configurable 👍

If we provide a default, but allow an override this would be best.

The standard FMTM user wouldn't necessarily need full control of the configuration, but to make it easier we could probably provide them some presets (such as major / minor roads)