Supplement to the Seata official documentation and extension of global transaction rollback strategies

## Why you need it?

In this official documentation, I think it's essential to provide the specific path to the documentation and the explicit configuration file. When local transactions outside the global transaction have manipulated some data, leading to inconsistencies between the snapshot information and the current data when the global transaction rolls back, what strategy has Seata implemented? What is the default logic and configuration? Alternatively, if Seata's inherent logic cannot meet user requirements, is there an available interface to pass context information and snapshot data, enabling users to customize certain rollback actions?

## Other related information

The issue names no files, tests, or entry points; start by locating Seata's official global-transaction rollback documentation and the configuration for snapshot conflicts. Done means documenting the relevant path, default rollback logic and configuration, and whether a supported context or snapshot customization interface exists.

Written by the indexing model from the issue text.