For multi-context generation, allow for a table regex

[sjh37]

The multi-context functionality was designed so you can fully control exactly what tables/columns are generated and how they are named. Mainly for security reasons, but also speed. No point having an app/service that can potentially query more data it should, not just tables, but columns. So the multi-context stuff is very prescriptive, it only spits out what you tell it to. Many small contexts are much faster than a single large context.

It would be helpful instead of specifying each table/column, you could also specify a regex for the tables you want.

The table regex will be additive to any you have already specified in MultiContext.[Table]

Do not use a regex for columns. If no columns are specified, then all will be used. However, if any columns are specified in MultiContext.[Column] then only those columns will be used.