Don't wrap usage to 80 columns

[BretJohnson]

Wrapping the usage message at 80 columns has a few downsides:

• It's inconsistent with the vswhere options, which wrap explicitly at sentence breaks and go as far as 105 columns currently.
• It looks a little funny with some of the descriptions wrapped aggressively, like the workload IDs below.

I'd suggest wrapping at maybe 100 or possibly 120 characters. Can see how that looks.
Could also not wrap at all automatically and add explicit line breaks in the option description, if that's not too hard, like vswhere behaves.

      --sku[=VALUE]          Edition, one of [e|ent|enterprise], [p|pro|
                               professional] or [c|com|community]. Defaults to '
                               community'.
      --mobile               -requires Microsoft.VisualStudio.Workload.
                               NetCrossPlat
      --xamarin              -requires Microsoft.VisualStudio.Workload.
                               NetCrossPlat
      --core                 -requires Microsoft.VisualStudio.Workload.
                               NetCoreTools
      --azure                -requires Microsoft.VisualStudio.Workload.Azure
      --data                 -requires Microsoft.VisualStudio.Workload.Data

[kzu]

This one is quite tricky since mono.options does the wrapping itself and it doesn't look customizable at all :/

[github-actions]

Due to lack of recent activity, this issue has been labeled as 'stale'.
It will be closed if no further activity occurs within 30 more days.
Any new comment will remove the label.