Currently, the frame type is represented as a Java enum. Unfortunately, this is not playing that nicely with new frame types (eg. coming from async-profiler) because the new frame type ID can not get mapped to any of the existing enum values and falls back to UNKNOWN .

The mapping also removes the type ID value and this makes supporting the new frame types a bit unwieldy as the JMC parser needs to be updated in order to be able to work with the new frame types.

My proposal is to extend the IMCFrame type with 'typeId' field which will hold the raw frame type ID and then could be used to distinguish between various UNKNOWN frames and allow working with new frame types which are not supported by JMC OOTB yet.

The proposal does not preclude adding these frame types to `IMCFrame.Type` enum if they turn out to be 'standard'.