Build(deps): bump github.com/seata/seata-go from 0.1.0-rc1 to 1.1.0

[dependabot]

Bumps github.com/seata/seata-go from 0.1.0-rc1 to 1.1.0.

Release notes

Sourced from github.com/seata/seata-go's releases.

v1.1.0

Seata-go 1.1.0 Released.

Seata-go is an easy-to-use, high-performance, open source distributed transaction solution.

The version is updated as follows:

feature：

• [#491] support query global lock key
• [#482] support multi delete SQL executor in AT
• [#481] support multi update SQL executor in AT
• [#478] support select for update SQL executor in AT
• [#477] support the json serialization method of undo log
• [#456] support insert on update SQL executor in AT
• [#444] support BZip2Compressor
• [#436] use rm config file
• [#433] support xa connect manager
• [#430] use getty config file

bugfix：

• [#509] fix undo log SQLType when execute insert on update SQL in AT
• [#495] fix undo log SQLType bug
• [#487] fix at bug when execute
• [#472] fix missing value of context When using global transactions
• [#461] fix the problem of error_code_test
• [#459] fix the rollback error log
• [#452] fix the error of id self-increment when executing insert sql in AT

optimize:

• [#507] refactor logic of multiple update sql in AT
• [#505] optimize multi SQL executor in AT
• [#453] optimize the messageType and transactionErrorCode enum
• [#447] optimize the datasource init process
• [#466] optimize variable naming

test:

• [#445] add unit test for TransactionErrorCode and MessageType

doc:

• [#492] update feature list of readme
• [#489] add change-log of version 1.1.0

contributors:

Thanks to these contributors for their code commits. Please report an unintended omission.

... (truncated)

Changelog

Sourced from github.com/seata/seata-go's changelog.

Release Notes

---

Commits

• adfc0ee doc: update change log of v1.1.0 (#512)
• 9d4b703 optimize: insert on update executor (#509)
• dd98cb7 docupdate 1.1.0 change log (#510)
• 54e502b doc: add v1.1.0 change log (#489)
• 7e49261 optimize multi update executor (#507)
• be1d75c Optimize multi delete of multi executor (#505)
• 39d8977 fix undo log sql type bug (#495)
• f2d7d8a reactor:multiple delete executor (#482)
• 93ec623 fix select for update bug (#491)
• 508795b doc: update readme (#492)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.