Baker/Dal: show injected attestations in logs

Context

Currently, the baker doesn't output in its logs any indication on the value of the injected DAL attestation. This MR extends the logs to show this information.

Fixes #4784 (closed)

Manually testing the MR

The following test

dune exec -- tezt/tests/main.exe --title "Alpha: Testing DAL node (dal attestor with baker daemon)"  --verbose

Now shows something like

[07:24:14.121] [baker2] Feb  7 08:24:14.121 - alpha.baker.actions: injected attestation op1ztfyQjHDQPAtDwhRhSiTwiqM5JAdgAeEYRVrGrFcD9oCJo1g with
[07:24:14.121] [baker2] Feb  7 08:24:14.121 - alpha.baker.actions: bitset 256 for bootstrap5 (tz1ddb9NMYHZi5UzPdzTZMYQQZoMub195zgv)

Instead of just

[07:24:14.121] [baker2] Feb  7 08:24:14.121 - alpha.baker.actions: injected attestation op1ztfyQjHDQPAtDwhRhSiTwiqM5JAdgAeEYRVrGrFcD9oCJo1g for
[07:24:14.121] [baker2] Feb  7 08:24:14.121 - alpha.baker.actions: bootstrap5 (tz1ddb9NMYHZi5UzPdzTZMYQQZoMub195zgv)

(which doesn't allow debugging which DAL slots are actually attested)

Checklist

• Document the interface of any function added or modified (see the coding guidelines)
• Document any change to the user interface, including configuration parameters (see node configuration)
• Provide automatic testing (see the testing guide).
• For new features and bug fixes, add an item in the appropriate changelog (docs/protocols/alpha.rst for the protocol and the environment, CHANGES.rst at the root of the repository for everything else).
• Select suitable reviewers using the Reviewers field below.
• Select as Assignee the next person who should take action on that MR