Multiple scoped imports via (reference) fail

To reproduce:

.foo {
	@import (reference) "abc";
	.one {
		.two(); // defined in abc.less
	}
}

in another file

.bar {
	@import (reference) "abc";
	.three {
		.two(); // defined in abc.less
	}
}

Current behavior:

The second use of .two() fails with "NameError: .two is undefined in ..."

Expected behavior:

Both references should work.

Environment information:

I don't think the env matters here, but...

• less version: 3 and 4
• nodejs version: 18
• operating system: Ubuntu 20.04

** Additional **

There is a workaround here by using:

	@import (multiple, reference) "abc";

The right behavior seems to me to be that the second reference should work because:

1. The first reference is scoped, and therefor abc.less is not actually getting included twice, in the sense that duplicate css is being produced.
2. It's a reference, and doesn't generate duplicate code anyway. Why not make the default 'multiple' to avoid the issue I had?
3. Treating references in the manner suggested here seems to be the more typical way that compilers treat libraries.

If a change isn't made to the code, it seems like it may be worthwhile to put this info into the documentation somewhere.

Start with the reproduction showing two scoped (reference) imports of abc.less, and trace how import scope and duplicate-import handling are resolved. Add a regression test covering both .two() calls, then verify that both references compile successfully without requiring the (multiple, reference) workaround.