chore: a better testing your workflows page

[ChunyiLyu]

Context

This is split out from #128.

Improving the Workflows is complex and doesn't have a clear goal

• Current
  • In this section, we introduce the following concepts today:
    • Pipeline design principles
    • A "test" framework for the promise
• Problem
  • Lots of boilerplate copy-and-paste. The "test framework" really complicates the entire page (lots to copy and paste, complex scripts we don't explain). The "test" doesn't actually "fail" -- the learner has to check the files themselves, but what are they looking for exactly?
• Improvement
  • Remove this section entirely? Move the TDD / Design Principles into a section of the Kratix documentation

Note that the test script we introduced in this section is used repeated in the later part of the workshop:

• Accessing Secrets and storing state
• Surfacing information via Status
  These sections use the test script to provide fast feedback to users and reply on it for docker build and kind load image. Keep this in mind if we need to shuffle Improving the Workflows around and do not break any of the following sections.

[ChunyiLyu]

cc @catmo-syntasso