OGR Provider: Support schema name other than "OGRSchema"

[jng]

Add support for a new DefaultSchemaName property, which if specified will be used instead of the hard-coded OGRSchema name for the feature schema.

[jng]

In 7656:

Add support for a new optional DefaultSchemaName property, which if specified will be used as the default schema name instead of "OGRSchema"

The primary motivation for this feature is to allow for OGR connections to SHP files to present the same schema/class structure and naming as SHP connections through its dedicated provider (the only real difference is in the schema name, which OGR had hard-coded as "OGRSchema" until now), which can then facilitate downstream tooling support in MapGuide to easily "swap" a SHP Feature Source to an equivalent OGR Feature Source and vice-versa. This can also apply for other data formats that are supported in both OGR and its dedicated FDO provider

A new unit test is included to exercise this new connection property

Fixes #953

[jng]

In 7657:

Merged revision(s) 7656 from trunk:
Add support for a new optional DefaultSchemaName property, which if specified will be used as the default schema name instead of "OGRSchema"

The primary motivation for this feature is to allow for OGR connections to SHP files to present the same schema/class structure and naming as SHP connections through its dedicated provider (the only real difference is in the schema name, which OGR had hard-coded as "OGRSchema" until now), which can then facilitate downstream tooling support in MapGuide to easily "swap" a SHP Feature Source to an equivalent OGR Feature Source and vice-versa. This can also apply for other data formats that are supported in both OGR and its dedicated FDO provider

A new unit test is included to exercise this new connection property

Fixes #953
........