Add dummy factory methods for ExecuteSuccessEvent and ExecuteFailureEvent

[hendrikmakait]

Addresses #6676 (comment)

• Tests added / passed
• Passes pre-commit run --all-files

[github-actions]

Unit Test Results

See test report for an extended history of previous test failures. This is useful for diagnosing flaky tests.

       15 files  ±  0         15 suites  ±0   6h 13m 51s ⏱️ - 16m 31s
  2 920 tests +  2    2 839 ✔️ +  2    79 💤  - 1  2 ❌ +1 
21 619 runs  +13  20 685 ✔️ +20  932 💤  - 8  2 ❌ +1 

For more details on these failures, see this check.

Results for commit 6a15062. ± Comparison against base commit f7f6501.

[gjoseph92]

What mypy madness makes this necessary?

[hendrikmakait]

mypy complains about type being used as a type for type and pyupgrade force-corrects from typing import Type.

[hendrikmakait]

Specifically, I think mypy is confused by type also being an instance variable on the dataclass.

[crusaderky]

but how comes it worked before?!?

[hendrikmakait]

mypy only got confused in the scope of dummy, where it suddenly had 3 options for type:

• instance variable
• type class
• function parameter

[gjoseph92]

Suggested change

	type_: Type | None = None,
	type: Type | None = None,

I think ideally, dummy would have the same signature as the non-dummy __init__.

[hendrikmakait]

Done, this was a remnant from mypy complaining about type being used as a type for type. I double-checked and switching the variable name is not a problem.

[crusaderky]

I removed the option to pass fields like exception, start, stop, etc. as they're all inconsequential to the worker state