Should "backtracking outside of &try scope" be a UsageError?

[awelzel]

Forgot to remove a backtrack() from a unit and eventually found a violation in the analyzer.log explaining the problem.

Would think this is an error that should make it into reporter.log and on stderr quickly (if not outright cause an exit) rather than be treated as a "violation". Might also be nice to detect this statically, but not sure if easy and/or possible even.

#fields ts      cause   analyzer_kind   analyzer_name   uid     fuid    id.orig_h       id.orig_p       id.resp_h  id.resp_p       failure_reason  failure_data
#types  time    string  string  string  string  string  addr    port    addr    port    string  string
1692782078.971564       violation       protocol        QUIC    CHhAvVGS1DHFjwGM9       -       xxx    yyy   443     backtracking outside of &try scope      \xcc\x00\x00\x00\x01\x10\x8...

[rsmmr]

Statically would be tricky, but yeah, makes sense to elevate this.