chore: Adding Litmus install manifest for 3.19.0

[S-ayanide]

Proposed changes

Adding Litmus install manifest for 3.19.0

Types of changes

What types of changes does your code introduce to Litmus? Put an x in the boxes that apply

• New feature (non-breaking change which adds functionality)
• Bugfix (non-breaking change which fixes an issue)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices applies)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have read the CONTRIBUTING doc
• I have signed the commit for DCO to be passed.
• Lint and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works (if appropriate)
• I have added necessary documentation (if appropriate)

Dependency

• Please add the links to the dependent PR need to be merged before this (if any).

Special notes for your reviewer:

[fcuozzo-shop]

Hello there @S-ayanide! Not sure where these manifests get copied over from but it looks like they are out of sync with the changes being made here? litmuschaos/chaos-operator#483 for example the cmdProbe/inputs/tolerations attribute is missing from the files merged via this PR?