2023 roadmap outline

[luisquintanilla]

We are excited to review your PR.

So we can do the best job, please check:

• There's a descriptive title that will make sense to other developers some time from now.
• There's associated issues. All PR's should have issue(s) associated - unless a trivial self-evident change such as fixing a typo. You can use the format Fixes #nnnn in your description to cause GitHub to automatically close the issue(s) when your PR is merged.
• Your change description explains what the change does, why you chose your approach, and anything else that reviewers should know.
• You have included any necessary tests in the same PR.

This PR updates the roadmap with goals through November 2023.

[ericstj]

LGTM!

[codecov]

Codecov Report

Merging #6444 (ed61480) into main (17c061a) will decrease coverage by 0.00%.
The diff coverage is n/a.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #6444      +/-   ##
==========================================
- Coverage   68.55%   68.54%   -0.01%     
==========================================
  Files        1170     1170              
  Lines      246977   246977              
  Branches    25792    25792              
==========================================
- Hits       169304   169302       -2     
- Misses      70950    70952       +2     
  Partials     6723     6723              

Flag	Coverage Δ
Debug	68.54% <ø> (-0.01%)	⬇️
production	62.95% <ø> (-0.01%)	⬇️
test	88.96% <ø> (ø)

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

Impacted Files	Coverage Δ
src/Microsoft.ML.Maml/MAML.cs	25.38% <0.00%> (-1.53%)	⬇️
...ML.Transforms/Text/StopWordsRemovingTransformer.cs	86.53% <0.00%> (+0.14%)	⬆️

[michaelgsharp]

Merging on red since this is just a markdown update and the test failure is unrelated.