Enhance Nightly Report to warn devs for new versions of dependencies

This is coming from @johanste . He is raising that we should be aware of when dependencies ship new major versions -- so that we can account for support for that major version if it makes sense for our customers.

We should start with a report per language repo that _audits_ this information. Produce a table that will appear on each `service`-specific build during the `Analyze` phase.

It should list:

- The dependency name
- The dependency version or version specifiers that we define for the packages within the current running service
- The latest version (preview or not) for that package -- REGARDLESS of the version specifiers that we have in our dependency definition

This should give us an early warning on major version ships for dependencies.

Eventually it would be good to actually attempt to install these major version revs, but notification is a good start.

Start by locating the nightly report implementation and the service-specific build's Analyze phase in the Azure SDK tools repository. Define the dependency data available for each language repository, then verify that the report table shows each dependency, its defined version or specifiers, and the latest preview or stable version regardless of those specifiers.

Written by the indexing model from the issue text.