Add Package vsix And Add getCommentperfixes Funtion

[JasonQWJ]

Add Package vsix And Add getCommentperfixes Funtion

Description of the change

Add a Launch :Package Extension
Add getCommentperfixes Funtion
Add Menus : Editor Context
Add more Code label And Comment Label

Motivation

Type of change

Feature request

Checklist

• [-] I have performed a self-review of my code.
• [-] I have added detailed comments to my code where applicable.
• [-] I have verified that my change does not break existing code.
• [-] My PR is based on the latest changes of the main branch (if unsure, please run git pull --rebase upstream main).
• [-] I am familiar with the Google Style Guide for the language I have coded in.
• [-] I have read through the Contributing Guide and signed the Contributor License Agreement.

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[markmcd]

Thanks for the contribution! Please sign the CLA so we can look at the code.

Without looking at the code it looks like there might be some things you can do first:

• Can this PR be split up at all? If there's some overarching feature being built that requires each of the changes, then that's OK, but if the changes can be made independently, that makes it easier to review (see our recommendation on small changes).
• Please make sure you either 1) link to an existing issue/FR or 2) explain why each change is being made - this helps us understand whether the changes are optimal.
• Don't check in binary files - for something like a vsix file, adding the metadata and build configurations would be OK, but don't include the package. Binaries can't be verified for tampering so can only be shipped by Google.

[JasonQWJ]

Thanks for the contribution! Please sign the CLA so we can look at the code.

Without looking at the code it looks like there might be some things you can do first:

• Can this PR be split up at all? If there's some overarching feature being built that requires each of the changes, then that's OK, but if the changes can be made independently, that makes it easier to review (see our recommendation on small changes).
• Please make sure you either 1) link to an existing issue/FR or 2) explain why each change is being made - this helps us understand whether the changes are optimal.
• Don't check in binary files - for something like a vsix file, adding the metadata and build configurations would be OK, but don't include the package. Binaries can't be verified for tampering so can only be shipped by Google.

Dear @markmcd ,

Thank you for your feedback. I have signed the CLA.

This is my first pull request, and I have deleted the binary files. I am not familiar with many of the rules, and it seems that my changes are only for my own needs and do not represent the ideas of others. In the future, I will submit some requests to fix bugs, etc. Therefore, I plan to cancel this request.

Thank you again for your feedback.

Best Regards,
Jason