Don't add probed warnings to config information.

[coke]

During configuration, all warnings that are successfully probed are entered into the parrot configuration. So if you built with gcc, you can run:

$ ./parrot_config -Wall
1

This seems like overkill, especially when:

./parrot_config ccwarn

seems sufficient. (ccwarn is empty in trunk, but what you'd expect in the rm_cflags branch.)

Feedback (esp. whether or not this constitutes a deprecation issue) welcome.

[Austin_Hastings]

It seems to me that if you're asking config questions, you are likely to be asking:

1. Show me the flags you built with. If you had different flags for different files (why?) then show me those.

2. Give me the set of flags that XX was built with, so I can build YY with the same.

Beyond that, I don't think there's much value in providing any other data.

[coke]

looks like the probed warnings are gone.