chore: update the roadmap after v1.3.0 release

[yizha1]

Description

What this PR does / why we need it:

Update the roadmap after v1.3.0 release

Which issue(s) this PR fixes (optional, using fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when the PR gets merged):

Fixes #

Type of change

Please delete options that are not relevant.

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] Helm Chart Change (any edit/addition/update that is necessary for changes merged to the main branch)
• [x] This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration

• [ ] Test A
• [ ] Test B

Checklist:

• [ ] Does the affected code have corresponding tests?
• [ ] Are the changes documented, not just with inline documentation, but also with conceptual documentation such as an overview of a new feature, or task-based documentation like a tutorial? Consider if this change should be announced on your project blog.
• [ ] Does this introduce breaking changes that would require an announcement or bumping the major version?
• [ ] Do all new files have appropriate license header?

Post Merge Requirements

• [ ] MAINTAINERS: manually trigger the "Publish Package" workflow after merging any PR that indicates Helm Chart Change

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

[junczhu]

JFYI, we may need to include Signed-off-by: Author Name authoremail@example.com in every commit message. You can also do this automatically by using the -s flag (i.e., git commit -s).

[yizha1]

@binbin-li can you take a look at this commit, it seems this one missed the sign-off. Please let me know how to fix it. Thanks. /cc @junczhu

Commit sha: 088154d, Author: Binbin Li, Committer: GitHub; The sign-off is missing.

[junczhu]

@binbin-li can you take a look at this commit, it seems this one missed the sign-off. Please let me know how to fix it. Thanks. /cc @junczhu

Commit sha: 088154d, Author: Binbin Li, Committer: GitHub; The sign-off is missing.

This is regarding to add or parse trailer lines that look similar to RFC 822 e-mail headers, at the end of the otherwise free-form part of a commit message. For example, in the following commit message

subject

Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Signed-off-by: Alice <alice@example.com>
Signed-off-by: Bob <bob@example.com>

the last two lines starting with "Signed-off-by" are trailers.

For convenience, a can be configured to make using --trailer shorter to type on the command line. This can be configured using the trailer..key configuration variable. The must be a prefix of the full string, although case sensitivity does not matter. For example, if you have

trailer.sign.key "Signed-off-by: " in your configuration, you only need to specify --trailer="sign: foo" on the command line instead of --trailer="Signed-off-by: foo".

Reference: https://git-scm.com/docs/SubmittingPatches#sign-off

cc\ @yizha1