Add support for sources that do not fit common query pattern

[yruslan]

Background

Currently, Pramen sources are either file, table, or query based: input.path=, input.table=, input.sql=.

But some sources do not fit this notion, and require different set of options to specify.

For instance, it could be data file / control file pairs.

Feature

Add the ability for a source to specify more complicated source paths than just one of the above list.

Example

  tables = [
    {
        input.data.file.1 = "s3://full/path/to/data.file1"
        input.control.file.1 = "s3://full/path/to/control.file1"

        input.data.file.2 = "s3://full/path/to/data.file2"
        input.control.file.2 = "s3://full/path/to/control.file2"

        input.data.file.3 = "s3://full/path/to/data.file3"
        input.control.file.3 = "s3://full/path/to/control.file3"
        ...
    }
  ]

Proposed Solution

Extend za.co.absa.pramen.api.Query trait with Custom case class that takes a Map[String, String] like this for the above example:

Map (
 "data.file.1" -> "s3://full/path/to/data.file1",
 "control.file.1" -> "s3://full/path/to/control.file1",
 "data.file.2" -> "s3://full/path/to/data.file2",
 "control.file.2" -> "s3://full/path/to/control.file2",
 ...