st2 trace list does not have the correct execution ID.

SUMMARY

st2 trace list does not have the correct execution ID. When an execution is made using the trace-tag, in the list of traces "st2 trace list" the execution ID is wrong in the last character, you can see that Stackstorm is adding the last character +1.

Example:
If the id of the execution is 61f98e7f0bd5ceba623a05c6, in the command "st2 trace list" the id of this execution is 61f98e7f0bd5ceba623a05c7

STACKSTORM VERSION

st2 3.6.0.post0, on Python 3.8.10

OS, environment, install method

helm instalation

Steps to reproduce the problem

run commands:

//given
st2 run core.local cmd=date --trace-tag="TEST-TRACE"
st2 run core.local cmd=date --trace-tag="TEST-TRACE"

//when
st2 trace list --trace-tag "TEST-TRACE"

//then
st2 execution get <ID_THAT_TRACE_LIST_SHOWS>

this should work but it doesn't. Because the ID is not the same ID of execution. The stackstorm chaged it adding +1 to the last character of the ID.

Expected Results

The id showing in trace list be correct and be equal of execution ID

Actual Results

The id in trace list is wrong

Start by reproducing the issue with the two st2 run core.local cmd=date --trace-tag="TEST-TRACE" commands, then compare the IDs from st2 trace list --trace-tag "TEST-TRACE" with st2 execution get. Trace where the trace list obtains and formats the execution ID; done means the displayed ID exactly matches the execution ID and can be retrieved successfully.