CueSettingLine.BadWhitespaceAfterDelimiter incorrect assertions

As it's been stated before, the test parsers used by the unit tests operate in a very liberal and permissive fashion. The test assumes that we are entirely skipping the setting because of some unexpected whitespace, however this behaviour is intended to be optional. Instead, the parser (including the original version) would report the unexpected whitespace rather than "bad value". In the future this will be marked as a "strict" error so that it's simple for the user to know that we want to throw away the setting, making the "optional"-ness simpler. But for what the test parser is actually doing, it should assert the actual syntax error is returned, not the "business rules" error.