Fix unknown ubsan crash types

[ViniciustCosta]

This should fix the following unknown ubsan crash types (https://screenshot.googleplex.com/6jTa2XjSfx8B6aQ.png):

• assumption is violated during execution
• slice bounds out of range [:-1]
• index out of range [-1]

TBD: add unit tests

b/473559705

[jonathanmetzman]

Can you do a query and check if there are others?

[ViniciustCosta]

Can you do a query and check if there are others?

Sure, here it is (probably not the best way to do it, but it confirms there aren't others): https://cloudlogging.app.goo.gl/Ff7E3wkP3VnrGdt17

[jonathanmetzman]

lgtm

[ViniciustCosta]

Actually, just found another one: Unknown UBSan crash type: upcast of null pointer of type (https://cloudlogging.app.goo.gl/xaZ8UXKAGnV62ofP8)

[ViniciustCosta]

Also, I think the out of range crashes are not actually UBSan, but rather an expected golang specific crash type that is not being correctly treated.

AFAICT all projects reporting these as unknown crash types are go project (jobs: libfuzzer_asan_mtail, libfuzzer_asan_gitea, libfuzzer_asan_openkruise) and even though the constants for these crash types exist (https://github.com/google/clusterfuzz/blob/master/src/clusterfuzz/stacktraces/constants.py#L338), they are reaching the UBSan codepath (probably due to runtime error: being the ubsan expected regex).