1438639a2f7eb9e9cba01454d3a9b1b16d179c9a removed a test
that was using undefined behaviour setting a non-typed enum
to a value outside its known range.
That test also checked if we formatted the value properly
when it could contain >1 valid enum value.
I don't think there's anything special about how we format
typed vs non-typed enums so I'm adding a test for ScopedEnum
that will expect to see 2 enum values plus extra.
I am just going to super nitpick here and say that these are not invalid values. When we have a fixed underlying type we are allowed to use the full range of the underlying type. The values may be outside the range of the enumerators but they are valid values.