Extract common JDBC configurations into their own fragment

[hashhar]

Split jdbc-type-mapping fragment into two. One for common JDBC connector configs and other for type mapping.

This will give a place to document common JDBC connector configurations as a follow-up.

[hashhar]

There are two versions of wording for the non-transactional inserts - 2af3981 and 2b6c52d. Please advise which one should be kept.

[findepi]

we shouldn't document things which have sensible defaults and generally don't need to be changed and exist only as a escape hatch.

i agree

[mosabua]

Fyi @jhlodin and @Jessie212

[jhlodin]

FYI: At @electrum 's request, Cherry-picked the JDBC type mapping fragments commit into its own PR here - #8727

[rosewms]

I agree with the feedback from Joe and Annie.

[hashhar]

@jhlodin @electrum I've simplified this to just be a refactor that splits 1 file into two. I hope this is not controversial.

The new common JDBC configs (from BaseJdbcConfig etc.) can now start getting documented under jdbc-common-configurations fragment.

[jhlodin]

Mostly LGTM, but the Phoenix connector doc is confusing. Left a comment with suggestions.

[m57lyra]

CREATE TABLE

[hashhar]

Pre-existing. Noted down, will fix in a later change. I'd like to keep this PR isolated to just mechanical splitting of things without changing unrelated things.

[rosewms]

I'd rephrase to remove "are available" it sounds awkward. I'd recommend something like:

Review the available Phoenix-specific configuration properties:

[mosabua]

Works for me to split it up.

[hashhar]

Squashed and merged.

[rosewms]

LGTM