`@escape.tech/graphql-armor-block-field-suggestions` leaves an extra `?` after masked suggestion

[kallja]

The @escape.tech/graphql-armor-block-field-suggestions package does what it promises. However, when masking suggestions, it leaves the leading whitespace and trailing question mark in place. I.E. the original unmasked message Cannot query field "i" on type "Node". Did you mean "id"? becomes Cannot query field "i" on type "Node". [Suggestion hidden]? without overriding the default mask. When mask is overridden with the empty string the result message is Cannot query field "i" on type "Node". ?.

I'd expect outputs of:

• Cannot query field "i" on type "Node". [Suggestion hidden] with default settings
• Cannot query field "i" on type "Node". with mask overridden with the empty string

[kallja]

If you're open to including this change (IMO an improvement, obviously), I'd be happy to contribute a PR implementing it.

[nullswan]

Sure! Looking forward the contribution @kallja :)