Reorganize "edit" docs

[mtoffl01]

Motivation

Make "edit" docs clearer

Changes

• Modified edit/README so it functions as a central place/ jumping off point to other docs
• Created new docs "add-new-test." "enable-test" and "skip-tests" which describe how to do the respective actions
• Deleted "egg-chicken-changes" doc. Believe the info in the "enable-test" doc covers this
• Updated the remaining docs to be clearer, more precise, and better catered to a newbie

Workflow

1. ⚠️ Create your PR as draft ⚠️
2. Work on you PR until the CI passes (if something not related to your task is failing, you can ignore it)
3. Mark it as ready for review
   • Test logic is modified? -> Get a review from RFC owner. We're working on refining the codeowners file quickly.
   • Framework is modified, or non obvious usage of it -> get a review from R&P team

🚀 Once your PR is reviewed, you can merge it!

🛟 #apm-shared-testing 🛟

Reviewer checklist

• If PR title starts with [<language>], double-check that only <language> is impacted by the change
• No system-tests internal is modified. Otherwise, I have the approval from R&P team
• CI is green, or failing jobs are not related to this change (and you are 100% sure about this statement)
• A docker base image is modified?
  • the relevant build-XXX-image label is present
• A scenario is added (or removed)?
  • Get a review from R&P team

[mabdinur]

Overall looks good to me. I think we can merge after all comments have been resolved.

[cbeauchesne]

I didn't finished my review, we'll chat by zoom to discuss around the concpet of parametric vs end-to-end

[mtoffl01]

@cbeauchesne calling this out because I deleted the egg-chicken-changes doc. I moved info about how to approach the "chicken or the egg" problem to the enable-test doc. I could link it here instead, but to be honest I don't know what this force-execute doc is referring to and whether it's relevant? 🤔