[Bug]: Fetching commitments by transaction id

[brancoder]

Bug description

Calling commitments endpoint with transaction Id instead of commitment id still resolves to a slot commitment instead of failing.
example:

tx id: 0x5f73f9666cc25bbbf553d71ff73034a61cb3f089214ff530c5b2909f35fce341ed680000
https://chronicle.iota2-alphanet.iotaledger.net/api/core/v3/commitments/0x5f73f9666cc25bbbf553d71ff73034a61cb3f089214ff530c5b2909f35fce341ed680000

response:
{"protocolVersion":3,"slot":26861,"previousCommitmentId":"0xfa247cd020b6a16536c4297eb06cbc6d49e9e21f3c0e3140a760b72b54de5245ec680000","rootsId":"0xd211d5cc1771de46ff023bce993c8e5a90f4101f5451d9b95d7d38abab240780","cumulativeWeight":"428823","referenceManaCost":"1"}