MIME4J-301 ContentTypeFieldImpl do fill a stacktrace when ended by a semicolon

While running some performance tests for the Apache James server, I noted a bunch of time spent filling some stacktraces while parsing some content types.

I noted that inputs like `Content-Type: text/plain;` was causing ContentTypeFieldImpl to fill some stacktraces while not preventing this class from doing a correct parsing.

As such, it make sense to me to consider such inputs as valid.
2 files changed