Rename core's "update system" component to "database update system"

Ever since the update.module went into core as "update.module" (instead of update_status, etc), there's all sorts of confusion about "update system" vs. "update.module". I don't have the bandwidth to closely follow the "update system" queue, so I frequently miss update.module issues that are incorrectly posted there. It's worse now that we have the Update manager, and there are parts of update manager (like authorize.php) that aren't part of update.module itself -- people appear to be even more prone to call such issues part of the "update system" (which makes perfect sense just given the names of the components). I've completely lost track of how many times I've had to move issues from the "update system" to "update.module" or vice versa. However, having to do it twice in the same issue was the straw that broke my back. I can't stand it anymore.

Can we please rename "update system" to "database update system" to attempt to disambiguate WTF that component is really for?

Thanks,
-Derek