Provide mechanism for managing resources across engines and executions

[marcphilipp]

The Platform should provide an extensible mechanism (ServiceLoader?) so that user code can create "closeable resources" that are injected as part of the context received by TestEngine implementations.

This feature is analogous to the ExtensionContext.Store concept from Jupiter but takes it to the Platform level. Moreover, it allows to reuse the same resource across multiple executions in a LauncherSession. We should advocate that resources stored in such a key-value store be immutable until their destruction. If such resources implement AutoCloseable they will get closed immediately before the LauncherSession they belong to is closed.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. Thank you for your contribution.

[stale]

This issue has been automatically closed due to inactivity. If you have a good use case for this feature, please feel free to reopen the issue.