feat: detailed steps output

[lowlighter]

Closes #485
This is a followup of #453

This PR introduces a detailed output:

• each step is logged whether it succeeded or not
  • failures, trace and info are displayed on associated step with correct indentation
  • range are expanded and display current key for easier loop tracking
  • Must failed assertions display the number of skipped steps

Also fix some issues:

• range step dump were overwritten because they had the same name
• failures in range exited the range loop rather than fallthrough (default behaviour of steps)
• -v and `` had actually the same verbosity level

Preview (-v output):

Preview (default output):

[nqb]

Hello @lowlighter,

Thanks for this improvement.

IMHO, we should be careful with display of variables directly in the output because they can contain sensitive informations.
I opened #476 recently and I wonder if it's not better to restrict variables into venom.log in place of STDOUT.

[lowlighter]

IMHO, we should be careful with display of variables directly in the output because they can contain sensitive informations. I opened #476 recently and I wonder if it's not better to restrict variables into venom.log in place of STDOUT.

I changed it to only display the only the range key instead. The value output is good in theory, but it can be very long and break the whole output in addition of the issue you mentioned (though I think that looping over secrets is a probably idea in the start)

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
2 Code Smells

68.1% Coverage
0.0% Duplication

[ovh-cds]

CDS Report build-venom-a#892.0 ✘

• Build
  • Build ✔
• Tests
  • Acceptance Tests ✘

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
1 Code Smell

66.0% Coverage
0.0% Duplication