Port update_advanced to D7

When we see how much update.module changes in D7 and what (if anything) we still need update_advanced for. ;) I guess one obvious answer are these:

#162788: Include modules that aren't enabled
#445748: Add hook_update_projects_alter()

So, yeah, we'll probably still need update_advanced... :/

Patches welcome if someone wanted to start porting to the latest UNSTABLE or something.

Not very itchy for me right now, so I doubt this is going to happen anytime soon if people wait for me to do it.

Don't forget developers who have to mark their modules to be ignored.

Yes, I do recall what update_advanced currently exists for. ;) I just have some fantasy that that's going to get into core somehow. Probably sheer fantasy. :(

Well, if I can get Coder to actually run in D7, I might take a look at a patch.

Assigning myself for a contrib upgrade code sprint.

That's great. However, with the 10/15 D7 core freeze looming, I'd vote that any of the following are more time-critical than this:

#555362: Support multiple download links in the available updates report (e.g. tar.gz + zip packages on drupal.org)
#238950: Reduce RAM resource consumption
#361563: Update Notifications causes SQL Server to go away
#319033: Weird order of projects listed on updates page
#237608: "Recommended version" for unsupported branch
#210144: If currently installed release is not found, update.module prints bogus information
#208766: Latest release from maintainer's recommended branch called "Also available", not "Recommended"

;)

Yeah, agreed. I wanted to wait until we hit post-freeze/slush/etc. Marking as postponed.