feat: add segmented (vueComponent#5568)

[selicens]

First of all, thank you for your contribution! 😄

New feature please send pull request to feature branch, and rest to master branch. Pull request will be merged after one of collaborators approve. Please makes sure that these form are filled before submitting your pull request, thank you!

[中文版模板 / Chinese template]

This is a ...

• New feature
• Bug fix
• Site / document update
• Component style update
• TypeScript definition update
• Refactoring
• Code style optimization
• Branch merge
• Other (about what?)

What's the background?

1. Describe the source of requirement. 分段控制器是AppleDesign风格的控件，在一定场景下有使用需求
2. Resolve what problem. 分段控制器（Segmented/Segmented Control）用于展示多个选项及其相关的信息，并允许用户选择其中单个选项，查看信息
3. Related issue link. (Added Segmented Segmented Controller component #5568)

API Realization (Optional if not new feature)

1. Basic thought of solution and other optional proposal. 参考了ant-design的segmented和ant-design-vue的tabs组件
2. List final API realization and usage sample.
3. GIF or snapshot should be provided if includes UI/interactive modification.
   

What's the effect? (Optional if not new feature)

1. Does this PR affect user? Which part will be affected? no
2. What will say in changelog? no
3. Does this PR contains potential break change or other risk? no

Changelog description (Optional if not new feature)

1. English description Segmented/Segmented Control is used to display multiple options and related information, and allow users to select a single option to view information
2. Chinese description (optional) 分段控制器（Segmented/Segmented Control）用于展示多个选项及其相关的信息，并允许用户选择其中单个选项，查看信息

Self Check before Merge

• Doc is updated/provided or not needed
• Demo is updated/provided or not needed
• TypeScript definition is updated/provided or not needed
• Changelog is provided or not needed

Additional Plan? (Optional if not new feature)

If this PR related with other PR or following info. You can type here.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.