What happened?

It seems that matchControllerRef does not work with Namespace-scoped resources introduced with v2.

How can we reproduce it?

A composition with two Namespace-scoped MRs from the AWS provider (preview) with one of them referencing the other through matchControllerRef.

What environment did it happen in?

Crossplane version: v2 preview