Unify case handling for boolean tag values

[michael2402]

We currently have:

• OsmUtils#getOsmBoolean() accepting all cases for true, yes, 1, on
• OsmUtils#isTrue(), OsmUtils#isFalse() accepting lower case true, yes, 1, on
• OsmPrimitive#isKeyTrue(key) accepting lower case true, yes, 1, on
• OsmPrimitive#hasAreaTags() accepts only yes
• Way#isOneway() accepting all cases for true, yes, 1, on and -1, but not reverse
• Relation map painting respects oneway=-1, but not reverse
• ReverseWayTagCorrector only accepting lower case, but accepting -1 and reverse

In tests:

• Highway#testWrongRoundabout: accepting all cases for true, yes, 1, on for oneway, but none of the reversed.
• UntaggedWay test accepts only noname=yes

That's what I found so far. We should unify this and decide on a common policy here.

[stoecker]

• as input we may accept more, e.g. getOsmBoolean() is base for tag dialogs, which accept many types, but always output yes or no.
• getOsmBoolean() is the generic function and should be used generally.
• otherwise we may accept only yes and no in many places (e.g. in drawing and for validity tests).
• oneway=reverse does not exist. Support of reverse is again one of the "accept many inputs"
• Why does ReverseWayTagCorrector only accept lower case? It calls OsmUtils#getOsmBoolean()?
• Generally true/false and on/off aren't really used anymore.

Conclusion:

• Use OsmUtils.
• Add an isReversedStrict() which does not accept "reverse"
• Way#isOneway() and painting should use OsmUtils#isReversedStrict()
• Places using only "yes" and "no" need not necessarily be changed.
• Maybe add also OsmUtils#getOsmBooleanStrict() only accepting "yes" and "no" (oneway=1 is used thought)