Task migration

[JorgeV92]

continue the migration of components from beman.task into beman.execution.

The main changes are:

• Add the public beman/execution/task.hpp header so users can refer to beman::execution::task.
• Move task-related implementation details into beman::execution::detail as part of the beman.task migration.
  The current branch keeps the task internals directly under beman::execution::detail. I would appreciate feedback on whether this layout is perfered, or whether the task-specific components should instead be grouped under a nested namespace such as beman::execution::detail::task for better modularization.
• Update allocator_support.hpp to better align with the allocator model described in P3980R1.

The task implementation is organized under include/beman/execution/detail/task/ instead of placing all task internals directly in detail/.

Current structure:

include/beman/execution/
├── execution.hpp
├── functional.hpp
├── stop_token.hpp
├── task.hpp
└── detail/
    └── task/
        ├── allocator_of.hpp
        ├── completion.hpp
        ├── error_types_of.hpp
        ├── handle.hpp
        ├── poly.hpp
        ├── promise_env.hpp
        ├── state_rep.hpp
        └── stop_source_of.hpp

all task related functionality will be added under /task.

[coveralls]

coverage: 95.481% (+0.04%) from 95.44% — JorgeV92:task-migration into bemanproject:main

[dietmarkuehl]

At the Croydon meeting the allocator_arg_t position was fixed to be the parameter of the coroutine function (and the allocator folllowing that, of course). Thus, find_allocator doesn't really need to recurse or could be omitted entirely.

[JorgeV92]

I was considering removing find_allocator.hpp entirely because the new allocator_support functionality handles the allocator-aware coroutine allocation path directly. I kept it for now because I was not fully sure whether there was still a use case that expected find_allocator to remain as a separate utility.

[dietmarkuehl]

This comment on the trailing #endif seems unusual. Maybe instead of fixing it remove it? In theory these comments should be added/removed by a code formatting tool like clang-format (I don't know if that actually does such transformations).

[JorgeV92]

Fixed. Might of forgot to run clang-format -i on this file