[EasyTest] Create EasyTestBundle

[alexndlm]

Q	A
Bug fix?	yes
New feature?	yes
BC breaks?	no
Deprecations?	no
Tests pass?	yes
Fixed tickets

We use \PHPUnit\Framework\Attributes\After to automatically check reported errors.
With After , our methods called after test tearDown, which always resets the container.
We need to use TraceableErrorHandlerStub as it stores reported errors in static property to not depend on the container.

[eonx-space-to-github-reviews]

Code Review in Space: https://eonx.jetbrains.space/p/support/reviews/703/timeline

[itorgov]

Code review approved. Keep up the good work!

Secure code in this PR has been written to best practice standards and covers the following as a minimum. Please ticket if coded this way (also tick if not relevant to this code change):

• Protect from Injection attacks
• Protect data with proper input validation, and protect against buffer overflows, pointers/shared data
• Protect with appropriate encryption and cryptography (E.g. Appropriate hashing, symmetric encryption used, ciphers) if applicable
• Protect against XSS and CSRF
• Ensure that pages, data access etc, are written with appropriate access control authorisation and authentication requirements
• Ensure all important errors and business logic cases are handled
• Ensure forwards and redirects are handled
• Ensure no sensitive data is exposed and appropriate logging in place as required

See procedure for more details: PROC-010 Secure Coding Practices

[roman-eonx]

Thanks @alexndlm. Excellent work! Code review complete.

Secure code in this PR has been written to best practice standards and covers the following as a minimum. Please ticket if coded this way (also tick if not relevant to this code change):

• Protect from Injection attacks
• Protect data with proper input validation, and protect against buffer overflows, pointers/shared data
• Protect with appropriate encryption and cryptography (E.g. Appropriate hashing, symmetric encryption used, ciphers) if applicable
• Protect against XSS and CSRF
• Ensure that pages, data access etc, are written with appropriate access control authorisation and authentication requirements
• Ensure all important errors and business logic cases are handled
• Ensure forwards and redirects are handled
• Ensure no sensitive data is exposed and appropriate logging in place as required

See procedure for more details: PROC-010 Secure Coding Practices