m, n, and k report 'none' in dtd traces

[DSMishler]

Using PaRSEC commit 7f81a1b (2023-01-19) and DPLASMA commit 75012ef3f (2023-01-23), the m, n, and k data in the trace of a GEMM is not present when using the dtd interface.

To Reproduce

1. Add the --force-profile flag to PARSEC_PTGPP_FLAGS in parsec/CMakeLists.txt
2. build command ../dplasma/configure --with-hwloc --with-mpi --with-blas=Intel10_64lp_seq --disable-debug -DPARSEC_PROF_TRACE=ON --prefix=$PWD/install
3. ./testing_dgemm_dtd -N 3000
4. turn the produced trace into an h5 file
5. check on the trace in your favorite software

trace_xsdk_dtd_lfq_2400_reforce.event_types[-5:]

MPI_DATA_PLD_SND         18
MPI_DATA_PLD_RCV         19
parsec_dtd_data_flush    20
Gemm                     21
Fake_FIRST_OUT           22


tevents = trace_xsdk_dtd_lfq_2400_reforce.events
tevents.loc[tevents['type'] == 21].head()



  | dc_key | priority | dc_dataid | tcid | trc | m | n | node_id | stream_id | taskpool_id | type | begin | end | flags | id | k
-- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | --
0 | 0 | 24 | 1 | 0 | None | None | 0 | 0 | 1 | 21 | 17248169 | 26838685 | 1 | 60 | None
0 | 0 | 24 | 1 | 0 | None | None | 0 | 0 | 1 | 21 | 26844096 | 27464702 | 1 | 62 | None
0 | 0 | 24 | 1 | 0 | None | None | 0 | 0 | 1 | 21 | 27467691 | 27778542 | 1 | 64 | None
0 | 0 | 24 | 1 | 0 | None | None | 0 | 0 | 1 | 21 | 27781289 | 28090761 | 1 | 66 | None
0 | 0 | 24 | 1 | 0 | None | None | 0 | 0 | 1 | 21 | 28093617 | 28354461 | 1 | 68 | None

</div>