Change set_value CPO to use member functions instead of tag_invoke

[msimberg]

Part of #1204. Changes the set_value CPO to dispatch to set_value member functions instead of using tag_invoke. No compatibility is provided for receivers still wishing to use tag_invoke.

The set_value member is mandated to be noexcept, so we static_assert inside the CPO to check that this is the case.

Consistently changes all set_value members to move the receiver by value into the set_value function scope, to emulate taking the receiver by value. With tag_invoke this was easily done by taking the receiver by value as a function parameter, but with a member function this isn't possible (without deducing this https://wg21.link/p0847), so we do the next best thing. I have not changed receivers in tests to consistently move the receiver into the function scope.

The change to a member function also triggers some compilation failures with nvcc not liking the PIKA_MOVE/PIKA_FORWARD macros. Given that #1325 is coming up soon anyway, I'm changing the offending places unconditionally to use std::move/std::forward.

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
✅ +0.16% (target: -1.00%)	✅ 95.31% (target: 90.00%)

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (28d528f)	18263	13780	75.45%
Head commit (c244be8)	18276 (+13)	13819 (+39)	75.61% (+0.16%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#1295)	64	61	95.31%

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

_{Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more}