Add more control over statement tracing

[nvamelichev]

Setting TRACE logging level for tech.ydb.yoj.repository.ydb.YdbRepositoryTransaction tends to produce overwhelmingly large log outputs.

We'd like to have more selective statement tracing, by e.g.

• Introducing a (YdbRepository- or YdbRepositoryTransaction-level) filter by (tx name, statement type and parameters, statement result/error),
• Encoding filterable information into logger name, e.g.: tech.ydb.yoj.repository.ydb.YdbRepositoryTransaction.<tx name>.<statement type>.{success|error}. This will be fully backwards-compatible, because enabling ALL traces by setting TRACE level for the tech.ydb.yoj.repository.ydb.YdbRepositoryTransaction top-level logger is still possible with this approach,
• Introducing a TxOptions- and TxManager-settable filter (just "trace/do not trace transactions created by this TxManager")
• Something else?

If we add new APIs for this functionality, they must be annotated as @ExperimentalApi and reference this issue.

[nvamelichev]

First Experimental API has been released in 2.6.25.

[nvamelichev]

TxManager-scoped setting has proven very useful: you can easily disable query tracing globally and then re-enable it for specific transactions.

There are currently no plans for a global (YdbRepository/YdbRepositoryTransaction-level) filter; and we've decided against encoding filterable information into the logger name.