As reported in D116303. I've taken the liberty of simplifying all the existing borrowed_range tests to
- be named borrowing.compile.pass.cpp
- use simple library types, specifically empty_view (is borrowed) and single_view (is not borrowed), wherever possible (the only place this isn't possible AFAICT is in common_view, where I left a comment)
- move range.ref.view into its own subdirectory, but not dig into that rabbit hole otherwise
- consistently test for adherence to concept borrowed_range, rather than constexpr bool enable_borrowed_range — the latter is equally technically correct, but the former is shorter, and also more like what the library user will actually do in practice. No user should ever query enable_borrowed_range directly.