Do not emulate annotations

[zbynek]

Fixes #10131

As pointed out the annotation doesn't have to be emulated at all since #10020 was fixed.

[zbynek]

Passing build https://github.com/zbynek/gwt/actions/runs/15096128855

[niloc132]

This looks right, but why stop here - we've got a few other emulated annotation types that can be removed too:
javax.annotation.Generated
javax.annotation.processing.Generated

org.junit.runner.RunWith
org.junit.runners.SuiteClasses

Do not remove javax.validation.Pattern, as it has inner types like Flag that can't be emulated any other way (though also might not technically be needed for emulation, but might possible be used downstream).

[zbynek]

This one is not an annotation, but

1. there is no use-case for throwing this from browser code
2. both methods declared by this class were missing from emulation

Probably better to remove than add the missing methods.

[niloc132]

That does seem like a weird one to be emulated - looks like it could have been a part of a push to emulate anything that can be emulated way back: 21eef3b

That would make it at least possible to handle such exceptions in gwt-rpc clients.

However in this case, since the Method can't be made into a field, without a custom field serializer, this can't work.

Normally I'd be inclined to say we shouldn't take away existing emulation that someone might be using... but I think this one is pretty sketchy to begin with.