docs: fix broken code block styling

[nekottyo]

Description

Fixed a broken layout caused by indentation of code blocks.

https://keptn.sh/latest/docs/components/lifecycle-operator/deployment-flow/?h=deployment+flow#pre-deployment-evaluation-phase

How to test

Please describe how to run the tests that you ran to verify your changes.
Provide instructions so we can reproduce.
Please also provide information about any automatic tests that you added.

• Manual Test A
• Unit Test B
• Integration Test C

Checklist

• [n/a] My PR fulfills the Definition of Done of the corresponding issue and not more (or parts if the issue is separated
  into multiple PRs)
• I used descriptive commit messages to help reviewers understand my thought process
• I signed off all my commits according to the Developer Certificate of Origin (DCO)
  see Contribution Guide
• My PR title is formatted according to the semantic PR conventions described in
  the Contribution Guide
• My code follows the style guidelines of this project (golangci-lint passes, YAMLLint passes)
• [n/a] I regenerated the auto-generated docs for Helm and the CRD documentation (if applicable)
• I have performed a self-review of my code
• [n/a] I have made corresponding changes to the documentation (if needed)
• My changes result in all-green PR checks (first-time contributors need to ask a maintainer to approve their test runs)
• New and existing unit and integration tests pass locally with my changes

Checks

• My PR fulfills the Definition of Done of the corresponding issue and not more (or parts if the issue is separated
  into multiple PRs)
• I used descriptive commit messages to help reviewers understand my thought process
• I signed off all my commits according to the Developer Certificate of Origin (DCO)(
  see Contribution Guide)
• My PR title is formatted according to the semantic PR conventions described in
  the Contribution Guide
• My content follows the style guidelines of this project (YAMLLint, markdown-lint)
• I regenerated the auto-generated docs for Helm and the CRD documentation (if applicable)
• I have performed a self-review of my content including grammar and typo errors and also checked the rendered page
  from the Netlify deploy preview
• My changes result in all-green PR checks (first-time contributors need to ask a maintainer to approve their test runs)

[sonarqubecloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[odubajDT]

Thank you for contribution!