demangler: CodeWarrior template specialization guards are incorrectly invalid #289
Description
An example would be @GUARD@mDefaultTagProcessor__Q36nw4hbm2ut17TextWriterBase<c>. This should demangle to nw4hbm::ut::TextWriterBase<char>::mDefaultTagProcessor guard based on existing guard behavior, but instead returns [invalid].
I'm unsure if this guard behavior exists outside of template specializations, but it is a known way of reproducing it.