Addon Koordinator

[MdSahil-oss]

Description of your changes

Adds Koordinator as an addon

How has this code been tested?

Checklist

I have:

• Title of the PR starts with type (e.g. [Addon] , [example] or [Doc]).
• Updated/Added any relevant documentation and examples.
• New addon should be put in experimental.
• Update addon should modify the version in metadata.yaml to generate a new version.

Verified Addon promotion rules

If this pr wants to promote an experimental addon to verified, you must check whether meet these conditions too:

• This addon must be tested by addon's e2e-test to guarantee this addon can be enabled successfully.
• This addon must have some basic but necessary information.
  • An accessible icon url and source url defined in addon's metadata.yaml.
  • A detail introduction include a basic example about how to use and what's the benefit of this addon in README.md.
  • Also provide an introduction in KubeVela documentation.
  • It's more likely to be accepted if useful examples provided in example dir.

[MdSahil-oss]

@wangyikewxgm @wonderflow This addon is done from my side, Please review it and let me know if I have to change or improve something :)

[wonderflow]

ping @FillZpp

[eahydra]

Thanks for your work.

[FillZpp]

There is no need to add definitions of Device, NodeSLO and NodeMetric, which are internal CRDs and all their CRs are created by koord-manager instead of users.

[MdSahil-oss]

@eahydra I've updated Readme for Fine-grained CPU Orchestration and Load Aware Scheduling scenes, would you like to have a look on that ?

[wonderflow]

generally LGTM, ping @eahydra @FillZpp

[eahydra]

@eahydra I've updated Readme for Fine-grained CPU Orchestration and Load Aware Scheduling scenes, would you like to have a look on that ?

@MdSahil-oss Thanks! Nice work！