For Import and Export a Separate Mapper Robot Should be Generated

[titusn]

Currently Build.xill generates one Mapper.xill robot that includes all mappings in a project. After solving #1, this should also be fixed. Expected behaviour would be to generate a separate Mapper.xill for config/import/ and config/export/ or a similar structure if you use multiple connectors for import or export. This is important, because it is more than likely that several connectors or import/export have overlapping naming for mappings and therefore need separate mapper robots. Also, while it may seem to make the project more complex by adding more separate files, it indeed makes the separate Mapper.xill robots more readable, because they only ever contain mappings for one system and one mapping.

Implement the expected behaviour by generating a separate mapper for each subfolder of config/ that contains a mapping/ directory. The resulting Mapper.xill MUST be stored in the subfolder, such that it may be included using for example include config.import.Mapper or include config.spimport.Mapper. Document the intended usage in a README.md.