[Feature][seatunnel-connectors-v2/connector-jdbc]sqlserver support bulk copy write

[chl-wxp]

Purpose of this pull request

Does this PR introduce any user-facing change?

How was this patch tested?

Check list

• If any new Jar binary package adding in your PR, please add License Notice according
  New License Guide
• If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs
• If necessary, please update incompatible-changes.md to describe the incompatibility caused by this PR.
• If you are contributing the connector code, please check that the following files are updated:
  1. Update plugin-mapping.properties and add new connector information in it
  2. Update the pom file of seatunnel-dist
  3. Add ci label in label-scope-conf
  4. Add e2e testcase in seatunnel-e2e
  5. Update connector plugin_config

[davidzollo]

Suggested change

	try {
	return connection.createStatement().executeQuery(queryMeta).getMetaData();
	} catch (SQLException e) {
	throw new SeaTunnelRuntimeException(
	JdbcConnectorErrorCode.NO_SUPPORT_OPERATION_FAILED,
	"get meta data fail:" + schemaTableName);
	}
	try (Statement statement = connection.createStatement();
	ResultSet resultSet = statement.executeQuery(queryMeta)) {
	return resultSet.getMetaData();
	} catch (SQLException e) {
	throw new SeaTunnelRuntimeException(
	JdbcConnectorErrorCode.NO_SUPPORT_OPERATION_FAILED,
	"get meta data fail: " + schemaTableName, e);
	}

[davidzollo]

Suggested change

	try {
	connection.rollback();
	} catch (SQLException rollbackEx) {
	log.error("Failed to rollback", rollbackEx);
	}

[davidzollo]

There‘s no need to handle rollback, JdbcOutputFormat will handle it

[davidzollo]

Suggested change

	connection.commit();

[davidzollo]

SeaTunnel self will handle commit

[davidzollo]

Is there any other types need to handle? like Decimal?

[davidzollo]

Is enabling table-level locks necessary?

[zhangshenghang]

Does it have to be schema.tableName? How about we allow users to only configure tableName, and in this case, the default schema will be used?

sink {
  Jdbc {
    // ...
    table = "my_target_table"  
  }
}

[zhangshenghang]

@chl-wxp This strong dependency will lead to a strong reliance, where mssql-jdbc is imported regardless of whether it is used, which is inconsistent with the previous design.
cc @davidzollo

[chl-wxp]

@chl-wxp This strong dependency will lead to a strong reliance, where mssql-jdbc is imported regardless of whether it is used, which is inconsistent with the previous design. cc @davidzollo

Thanks for the reminder. Such strong dependency is indeed a problem. I need to think about how to solve this problem.