Update root readme to provide more clarity

[ramya-rao-a]

This PR updates the root readme to

• remove reference to "November" releases. This was added a year ago to refer to our first wave of releases
• add more clarity on the different kinds of packages this repo houses
• removes the difference between old and newer versions of the packages that follow the Azure SDK guidelines. For an end user that lands in the repo readme, it does not make a difference as to whether the package is Track 1 or Track 2. They would only care about what packages live here and what can they be used for

[xirzec]

I like the updates!

[check-enforcer]

This pull request is protected by Check Enforcer.

What is Check Enforcer?

Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass.

Why am I getting this message?

You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged.

What should I do now?

If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows:
/check-enforcer evaluate
Typically evaulation only takes a few seconds. If you know that your pull request is not covered by a pipeline and this is expected you can override Check Enforcer using the following command:
/check-enforcer override
Note that using the override command triggers alerts so that follow-up investigations can occur (PRs still need to be approved as normal).

What if I am onboarding a new service?

Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment:
/azp run prepare-pipelines
This will run a pipeline that analyzes the source tree and creates the pipelines necessary to build and validate your pull request. Once the pipeline has been created you can trigger the pipeline using the following comment:
/azp run js - [service] - ci

[ramya-rao-a]

/check-enforcer override

[nickzhums]

thanks for this change @ramya-rao-a looks good to me. One question - do we plan to re-organize other languages root readme like this as well?

[ramya-rao-a]

do we plan to re-organize other languages root readme like this as well

I'll work with @lmazuel to make a similar update to the Python repo.
Python and TypeScript SDKs are in the same boat because all the Track 2 mgmt plane packages and most of the Track 1 data plane packages use the same package name as Track 1. So it is less relevant to differentiate between the two. I will leave it to @AlexGhiondea and @joshfree to decide whether .NET and Java repos want to follow the same format or not.

[nickzhums]

@ramya-rao-a makes sense - thanks!

[ramya-rao-a]

/check-enforcer override