Continue to modernize Drush use of Symfony Console and Annotation Commands

[greg-1-anderson]

• Command dispatching
  • Decide how to test requirements, and filter out commands where they are not met
  • Redispatch to remote servers
• Bootstrapping
  • Make bootstrapping of global command classes dependent on their implementation of BootstrapAwareInterface, give them a reference to Boot via setter injection Add bootstrap aware interface consolidation/bootstrap#1
  • Bootstrap object should be able to provide specific implementations of certain services (e.g. SQL access).
• Option processing
  • Allow default options to be specfied for global commands
  • Handle --global-option=0 options
  • Handle --no-global-option synonyms
• Configuration file handling
• Alias file handling
• Backend invoke
• SQL classes
• Output formatting
  • Decide what to do with unusual formats
    • message (Only used by search-status command. Drop & replace with a key-value --list?)
    • variables (Unused?)
    • config (*Default format for site-alias command, pipe format for variable-get command. Drop and replace with yaml?)
    • labeled-export (Unused?)
    • html (Used by help)
• Existing command compatibility layer
  • Create a wrapper Symfony Command to call old commands and hooks from the Symfony Application dispatcher
    • Determine mapping from Drush procedural hooks to new hooks Determine mapping from Drush procedural hooks to new HookManager #2116
  • Ensure that Drush notify still works with Symfony commands
• Help changes Help command for annotation classes #2106
  • The list command shows command aliases as duplicate entries; duplicates should be hidden
  • All aliases and all usages appear in the "Usage" section; should be split up
  • All global options are shown all the time
  • @topic is needed, so help text can show related topics

See #2103 for additional items already done and merged.

[greg-1-anderson]

Continued in #2843.