Refactor E2E libs to avoid using negative language

What does this MR do?

• Add documentation surrounding the usage of negative expectations in e2e specs
• Refactor existing specs and libraries not_to use negative language
• Add another bad example of block arg naming for resource

Does this MR meet the acceptance criteria?

Conformity

• [-] Changelog entry
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• [-] Database guides
• [-] Separation of EE specific content