Fix schedule_all move-only range support

[fallintoplace]

What changed

• forward the range when building the schedule_all operation state
• add a regression test with a move-only owning_view

Why

The consuming subscribe() path moves the range, but opstate_base_with_receiver passed its by-value range parameter as an lvalue. That made valid move-only ranges fail to compile.

Testing

• build/test/exec/test.exec 'schedule_all on static_thread_pool accepts move-only ranges'
• build/test/exec/test.exec

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[ericniebler]

/ok to test 43f0b4a