Work around issue 22619 - Avoid Nullable copy ctor unless required

[kinke]

Copy ctors are still buggy, so unconditionally adding one for Nullable is everything but a non-breaking change (and was added in the 2.098.1 point release - #8318).

[dlang-bot]

Thanks for your pull request and interest in making D better, @kinke! We are looking forward to reviewing it, and you should be hearing from a maintainer soon.
Please verify that your PR follows this checklist:

• My PR is fully covered with tests (you can see the coverage diff by visiting the details link of the codecov check)
• My PR is as minimal as possible (smaller, focused PRs are easier to review than big ones)
• I have provided a detailed rationale explaining my changes
• New or modified functions have Ddoc comments (with Params: and Returns:)

Please see CONTRIBUTING.md for more information.

---

If you have addressed all reviews or aren't sure how to proceed, don't hesitate to ping us with a simple comment.

Bugzilla references

Auto-close	Bugzilla	Severity	Description
✗	22619	regression	[REG2.098.1] Nullable regression introduced by new copy ctor

Testing this PR locally

If you don't have a local development environment setup, you can use Digger to test this PR:

dub run digger -- build "stable + phobos#8358"

[burner]

does this also make it work with the nullable function?

[kinke]

does this also make it work with the nullable function?

Depends on T. Symmetry's REPL finally compiles with this.

[burner]

@RazvanN7 this seems to be fixing my problem as well.

thank you @kinke

[burner]

I'm happy that this is fixed, but

this(ref return scope inout Nullable!T rhs) inout

having all these keywords on a ctor is just mad.