lib/tapi: stop logging jump set/remove at INFO by default

[okt-konst]

lib/tapi/tapi_jmp.c is the only file in the tree that defines
TE_LOG_LEVEL 0xff, which forces every log level on. As a result each
tapi_jmp_push() / tapi_jmp_pop() emitted an INFO line, and since every
TAPI_ON_JMP and CHECK_RC pushes a jump point, the log filled with a
set/remove pair per guarded call. It is particularly overwhelming in suites
that guard heavily.

This demotes the two per-call traces to VERB and sets the file level to
TE_LL_INFO. The rare "Jump from" trace, logged only on an actual
longjmp(), stays visible. Raising the level to include TE_LL_VERB
restores the old behaviour when debugging push/pop is wanted.

Testing: engine and agent build clean, no new warnings; verified the
per-call lines disappear from the log while "Jump from" is retained.

[arybchik]

Defining TE_LOG_LEVEL is definitely ugly. However, these logs are very useful in C tests. Otherwise sometimes it is hard to understand what's going on.

First of all I think it should be fixed to use TE_LOG() directly, drop TE_LOG_LEVEL define and keep INFO log level.

As the second step I don't mind to make it VERB as long as it is available in logs (not dropped).

Third more fine-grained control could be added to control these logs.

[k0nstantin]

As the second step I don't mind to make it VERB as long as it is available in logs (not dropped).

I was under impression that VERB is not in the logs by default.

[arybchik]

As the second step I don't mind to make it VERB as long as it is available in logs (not dropped).

I was under impression that VERB is not in the logs by default.

See the first step

[k0nstantin]

For the record - things are bad, because JS code that builds the HTML logs relies on the bloody setjump log. Because..... arr.

Thinking