Enable options to index creation on maps (solves issue 122)

[sl-at-ibm]

Fixes #122 .

This PR enables passing the options (ascii/normalize/caseSensitive) to index creation for a map table column.

Along the way:

1. xmldoc params are aligned with the actual methods in TableIndexBuilder (+their text added where it was missing);
2. said options are encapsulated in the proper TableIndexOptions to avoid three anonymous booleans in a row (incl. non-table index creation). this is a breaking change (see tests), which anyway we have discussed in 122 already.
3. added tests for this index creation pattern.

Note: as a matter of fact, the Data API accepts these options when creating keys/values indexes only, whereas for "entries creation" there is only one allowed combination of the three bools (the default), which renders it unnecessary to specify them. However, preventing the user from supplying the options is probably not a task for the client under the philosophy of not duplicating server-side guardrails. Hence no checks are performed ("if mapindextype == entries ...").

[sl-at-ibm]

@a-random-steve FYI ^