chore: bump version to 2.0.0

[fly602]

update changelog to 2.0.0

Summary by Sourcery

Chores:

• Bump Debian package version to 2.0.0 in debian/changelog

[sourcery-ai]

Reviewer's Guide

This PR bumps the Debian package version by updating the top entry in the debian/changelog to reflect the new 2.0.0 release.

File-Level Changes

Change	Details	Files
Update Debian changelog for new version	Replace version number 1.99.22 → 2.0.0 Update release date to current date	debian/changelog

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @fly602 - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[github-actions]

TAG Bot

TAG: 2.0.0
EXISTED: no
DISTRIBUTION: unstable

[deepin-ci-robot]

deepin pr auto review

在审查这个提交的 changelog 文件时，我注意到以下几点：

1. 版本号更新：提交中提到版本号从 1.99.21 更新到 2.0.0，这是一个重大更新，通常意味着引入了新的功能或进行了重大重构。确保这个版本号的更新是合理的，并且与实际代码更改相匹配。

2. 提交信息：提交信息中提到了 feat: update session configuration for Deepin Desktop Environment，这表明更新了会话配置。请确保这个功能确实已经实现，并且与 2.0.0 版本号相符。

3. 日期格式：提交日期格式为 Fri, 20 Jun 2025 16:59:39 +0800，这是一个标准的 RFC 2822 日期格式。确保这个日期是准确的，并且反映了实际提交的时间。

4. 签名：提交信息以 -- fuleyi <fuleyi@uniontech.com> 结尾，这是一个标准的 Debian 提交签名格式。确保这个签名是正确的，并且提交者有权进行这个提交。

5. 格式一致性：提交信息中的格式应该与项目中的其他提交保持一致。确保所有提交信息都遵循相同的格式和风格。

6. 版本号管理：在更新版本号时，确保遵循项目的版本号管理策略。通常，版本号会遵循语义化版本控制（Semantic Versioning），即主版本号、次版本号和修订号。

7. 变更日志：在更新 changelog 文件时，应该同时更新项目的变更日志（CHANGELOG.md 或其他相关文档），以便其他开发者了解版本更新内容。

总结：这个提交的 changelog 文件看起来是合理的，但是需要确保版本号更新和功能实现是正确的，并且遵循项目的版本号管理和提交信息格式规范。

[deepin-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: fly602, xionglinlin

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• debian/deepin/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment