chore: add shining-n to deepin-kwin-team

[justforlxz]

add team member

Log:

[github-actions]

CLA Assistant Lite bot:

如果你是以企业贡献者的身份进行提交，请联系我们签署企业贡献者许可协议
If you submit as corporate contributor, please contact us to sign our Corporate Contributor License Agreement

感谢您的提交，我们非常感谢。 像许多开源项目一样，在接受您的贡献之前，我们要求您签署我们的个人贡献者许可协议。 您只需发布与以下格式相同的评论即可签署个人贡献者许可协议。
Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Individual Contributor License Agreement before we can accept your contribution. You can sign the Individual Contributor License Agreement by just posting a Pull Request Comment same as the below format.

---

I have read the CLA Document and I hereby sign the CLA.

---

lxz seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You can retrigger this bot by commenting recheck in this Pull Request}

[deepin-ci-robot]

deepin pr auto review

我来对这个Git diff进行审查：

1. 语法逻辑：

• 修改内容是在teams.yaml文件中添加了一个新的团队成员"Shining-N"到某个团队中
• 语法完全正确，使用YAML的标准格式，通过添加"- Shining-N"来新增成员
• 缩进保持一致，符合YAML规范

2. 代码质量：

• 修改简单明确，只添加了一个新成员
• 保持了与现有代码风格的一致性
• 没有多余的空白字符或格式问题

3. 代码性能：

• 这种配置文件的修改不会影响运行时性能
• YAML文件通常在程序启动时加载一次，添加一个成员对性能影响微乎其微

4. 代码安全：

• 添加新成员本身不会带来安全风险
• 但建议确认：
  • "Shining-N"是否是正确的用户名
  • 该用户是否应该被添加到这个团队
  • 该用户是否需要triage权限

改进建议：

1. 建议在提交信息中说明添加该成员的原因
2. 如果这是一个重要的权限变更，建议通过PR review流程让更多人知晓
3. 可以考虑添加注释说明新成员的职责或权限范围

总的来说，这是一个简单、清晰、格式正确的修改，没有明显的问题。只要确认添加该成员的决策是正确的，这个修改就可以接受。

[deepin-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: BLumia, justforlxz

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