Support version detection of core libraries when implemented through drupal_process_attached (drupal_add_library)

This issue is a followup to #1787222: [meta] Strategy for updating vendor JS libraries within a major stable version →

The major concepts of version detection are addressed in the Libraries API contrib module and described here in detail:

http://drupal.org/node/1342220#libraries-detection

The resolution bullet points from #1787222 that require this followup are:

1. Calls to drupal_add_library() don't specify version, just the library. If you want a specific version, register your own custom library in hook_library_info(), list the dependency that JS code has, and then call drupal_add_library() of that custom library.
2. When Drupal renders the scripts for the page (e.g., within drupal_get_js() or similar), it looks at the entire list of libraries added to the page, and runs some algorithm to determine which version of each library to provide: requiring compatibility, and among options that are all compatible, choosing the maximum. Details of this algorithm TBD.

This issue addresses the TBD of point #2.