chore(probe): Adding the root cause into probe description

[ispeakc0de]

Signed-off-by: Shubham Chaudhary shubham.chaudhary@harness.io

What this PR does / why we need it:

Sample probe descriptions

HTTP Probe

- Probe responded with a invalid output. Actual value: 200 is not greater than Expected value: 400

- The URL https://litmuschaos.io did respond with correct status code. Actual and Expected status codes are 200 and 200 respectively

- Get "https://litmuschaos.io": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

Cmd Probe

- Probe responded with a valid output. Actual and Expected values are ‘shubham’ and ‘shubham’ respectively

- Probe responded with a invalid output. Actual value: shubham doesn't matched with any of the Expected values: [hello world]

 - Either probe is not executed or not evaluated

K8s Probe

-  Probe is successfully performed the 'absent' operation on kubernetes resource

- no resource found with provided {labelSelectors: app=nginx, fieldSelectors: “”} selectors

- resource with provided {labelSelectors: app=nginx, fieldSelectors: “”} selectors should not exists, found 1 resource with matching selectors

PromProbe:

- Probe responded with a valid prometheus metrics value. Actual and Expected status values are 19565 and 100 respectively

- Probe responded with a invalid output. Actual value: 19823 is not lesser than Expected value: 100

- unable to run command, error: error querying prometheus: Post "http://35.184.156.158:31090/api/v1/query": context deadline exceeded

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #

Special notes for your reviewer:

Checklist:

• Fixes #
• PR messages has document related information
• Labelled this PR & related issue with breaking-changes tag
• PR messages has breaking changes related information
• Labelled this PR & related issue with requires-upgrade tag
• PR messages has upgrade related information
• Commit has unit tests
• Commit has integration tests
• E2E run Required for the changes

[neelanjan00]

CI pipelines are failing; can you PTAL?

[arkajyotiMukherjee]

Looks good. Thanks @ispeakc0de

[ksatchit]

Looks good.