Fix missing/outdated pass options in PassRegistry.def

[mjulian31]

There are a handful of passes in PassRegistry.def with outdated or missing pass options. These strings describing pass options are used for the printPassNames() function only, which is likely why they have gotten out-of-date without being caught. This MR simply changes the few passes where the option string is out-of-date, fixing the output of -print-passes. This does not affect functionality of the pipeline parser, and is hard to verify in a unit test, so no tests were added.

[AlexMaclean]

Nice, LGTM. I wonder if it would be possible to write a test to ensure these options remain up-to-date

[nikic]

I think to meaningfully improve it we need a new, more declarative mechanism to declare pass options (at least for the simple cases). The current one is annoyingly ad-hoc.

[mjulian31]

Yeah I considered adding a test but wasn't sure how to frame it. The real source of truth for pass options are the parsing functions, and there isn't a great way to extract all possible options from these as they are all structured a little differently. I suppose you could catch old options that don't exist any more by just testing every option, but it wouldn't help with new missing options, which seemed to be the main problem. I agree it would be a bigger change needed to declare them more systematically.