[Proposal] add yurtadm proposal

[windydayc]

What type of PR is this?

/kind feature
/kind design

What this PR does / why we need it:

add yurtadm proposal.

Special notes for your reviewer:

/assign @rambohe-ch
/assign @Peeknut

[openyurt-bot]

@windydayc: GitHub didn't allow me to assign the following users: your_reviewer.

Note that only openyurtio members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line:
/kind bug
/kind documentation
/kind enhancement
/kind good-first-issue
/kind feature
/kind question
/kind design
/sig ai
/sig iot
/sig network
/sig storage
/sig storage

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

other Note

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openyurt-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: windydayc
To complete the pull request process, please assign fei-guo
You can assign the PR to them by writing /assign @fei-guo in a comment when ready.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (master@475c156). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #902   +/-   ##
=========================================
  Coverage          ?   43.66%           
=========================================
  Files             ?       83           
  Lines             ?    11260           
  Branches          ?        0           
=========================================
  Hits              ?     4917           
  Misses            ?     5908           
  Partials          ?      435           

Flag	Coverage Δ
unittests	43.66% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[rambohe-ch]

@windydayc because sealer can not support render openyurt version info into kubefile, so it's not convenient to build OpenYurt cluster image in a github action pipeline.

and we need to follow the sealer progress, then we can add a new pipeline when sealer supports it. so i will close this proposal now.