[New Engine] Add new ThreadPoolTaskRunner and new PrefectFuture implementation

[desertaxle]

This PR creates a new interface for task runners and prefect futures to work with the new engine. The new ThreadPoolTaskRunner is intended to replace the existing ConcurrentTaskRunner. The new PrefectFuture implementation is meant to serve as a wrapper for specific future implementations. More implementations will be added when we update the Dask and Ray task runners.

This PR turns on the logic to run the existing task tests through the new engine to ensure compatibility and expose differences.

Two main differences are:

1. .submit on a task is always a sync call
2. .result and .wait on a PrefectFuture are always sync calls

Example

Example of a flow submitting tasks to a ThreadPoolTaskRunner (should look familiar)

from time import sleep

from prefect import flow, task


@task
def task_the_first():
    sleep(10)
    return "hello"


@task
def task_the_second(thing_to_say):
    print(f"Upstream told me to say {thing_to_say}")


@task
def task_the_third():
    print("I'm the third task")


@flow
def my_flow():
    future1 = task_the_first.submit()
    future2 = task_the_second.submit(future1)
    task_the_third(wait_for=[future2])


if __name__ == "__main__":
    my_flow()

Checklist

• This pull request references any related issue by including "closes <link to issue>"
  • If no issue exists and your change is not a small fix, please create an issue first.
• If this pull request adds new functionality, it includes unit tests that cover the changes
• This pull request includes a label categorizing the change e.g. maintenance, fix, feature, enhancement, docs.

For documentation changes:

• This pull request includes redirect settings in netlify.toml for files that are removed or renamed.

For new functions or classes in the Python SDK:

• This pull request includes helpful docstrings.
• If a new Python file was added, this pull request contains a stub page in the Python SDK docs and an entry in mkdocs.yml navigation.

[desertaxle]

Some of the tests differ between the current engine and the new engine due to the sync-only nature of the new task runner and PrefectFuture interfaces

[desertaxle]

Result retrieval is a sharp edge in the new engine. @sync_compatible will return a coroutine for State.result() when called from a sync context if there is an active event loop. We likely need a sync implementation for State.result().

[cicdw]

from sync review + read through, I think this looks good