chore(deps): bump com.google.code.gson:gson from 2.12.1 to 2.13.0

[dependabot]

Bumps com.google.code.gson:gson from 2.12.1 to 2.13.0.

Release notes

Sourced from com.google.code.gson:gson's releases.

Gson 2.13.0

What's Changed

• A bug in deserializing collections has been fixed. Previously, if you did something like this:

  gson.fromJson(jsonString, new TypeToken<ImmutableList<String>>() {})
  

  then the inferred type would be ImmutableList<String>, but Gson actually gave you an ArrayList<String>. Usually that would lead to an immediate ClassCastException, but in some circumstances the code might sometimes succeed despite the wrong type. Now you will see an exception like this:

  com.google.gson.JsonIOException: Abstract classes can't be instantiated!
  Adjust the R8 configuration or register an InstanceCreator or a TypeAdapter for this type.
  Class name: com.google.common.collect.ImmutableList
  

  because Gson now really is trying to create an ImmutableList through its constructor, but that isn't possible. Either change the requested type (in the TypeToken) to List<String>, or register a TypeAdapter or JsonDeserializer for ImmutableList.

• The internal classes $Gson$Types and $Gson$Preconditions have been renamed to remove the $ characters. Since these are internal classes (as signaled not only by the package name but by the $ characters), client code should not be affected. If your code was depending on these classes then we suggest making a copy of the class (subject to the license) rather than depending on the new names.

Full Changelog: google/gson@gson-parent-2.12.1...gson-parent-2.13.0

Commits

• bfe0fd5 [maven-release-plugin] prepare release gson-parent-2.13.0
• 6ed64ca add multi-catch support to the code base (#2841)
• 0074376 Bump the maven group with 3 updates (#2840)
• 45e5e14 Rename $Gson$Preconditions and $Gson$Types. (#2838)
• c6d4425 Remove obsolete comment in pom.xml (#2835)
• 9afd6f8 Bump the maven group with 10 updates (#2831)
• ad5371e Fix findings that are new with the latest Error Prone. (#2834)
• de190d7 Restructure code to avoid assignment expression warning. (#2833)
• 3d66847 Bump the github-actions group with 3 updates (#2832)
• 2549ba9 Fix ConstructorConstructor creating mismatching Collection and Map instances ...
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)

[github-actions]

Thanks for your PR. 🙏
Please check again for your PR changes whether they contain any usage configuration change, such as Add new configuration or Change default value of configuration.
If so, please add or update documents (Markdown format) in the docs/ directory of the repository smart-doc-group/smart-doc-group.github.io.

In addition, if you have added new features, please provide example code in the repository smart-doc-group/smart-doc-example-cn. This will help other users understand how to use the new features.

Code Style Reminder:
The code should use the Spring code style. Please format your code using the command mvn spring-javaformat:apply. You can also install the Spring Java Format plugin for convenience.

---

感谢您提交的PR。 🙏
请再次查看您的PR内容，确认是否包含任何使用方式或配置参数的变更，如：新增配置参数、修改默认配置等操作。
如果是，请确保在提交之前，在仓库smart-doc-group/smart-doc-group.github.io中的docs/目录下添加或更新文档（Markdown格式）。

另外，如果您添加了新功能，请在仓库smart-doc-group/smart-doc-example-cn中提供示例代码。这将帮助其他用户了解如何使用新功能。

代码风格提示：
请使用 Spring 代码风格。您可以通过命令 mvn spring-javaformat:apply 格式化代码。为了方便操作，您还可以安装 Spring Java Format 插件。