[clapack, lapack-reference] Add conflict messages

[NancyLi1013]

Describe the pull request

• What does your PR fix? Fixes lapack-reference:x64-windows build failure #13054

clapack and lapack-reference cannot be installed at the same time, since both of them will install lib/lapack.lib.

Note: No need to test features.

[cenit]

Since there might appear even other provider of lapack in future (there are many vendor), what about using the strategy adopted in opencv (where there are already v2, v3 and v4 here on vcpkg, that have to be exclusively installed)?
The idea is that if you just look at the artifact library you cannot really check who installed it if there might be 2 more other ports, so I relied on looking at the share/${PORT} Folder.
In this case I can pinpoint the real source of troubles
Please let me know if I was not clear enough

[JackBoosY]

@cenit But these two ports are different, not a higher or lower version of the same port.

[cenit]

No I mean...
In case we add a third lapack implementation, which will provide lapack.lib like these, this message will have to be reworked in order to identify the port already installed.

Let's assume port A, B and C provide lapack.lib. If you have installed B and then you ask to install A, in order to tell you that you have to remove port B, vcpkg needs to check for the presence of share/B. This is the only robust way to identify colliding ports.
Otherwise looking only at lapack.lib, you cannot say if it was provided by B or C during A installation...

[JackBoosY]

@cenit make sense.

[cenit]

That's the only similarity with opencv2/3/4 ;)

[BillyONeal]

@NancyLi1013 @JackBoosY When we edit alternatives like this make sure to double check the ones that CI is not testing manually.

[BillyONeal]

Thanks for your contribution!

[joavd]

I have a problem related to this, can't install Clapack due to lapack.lib being installed already from lapack-reference.
Vcpkg is already updated, any known fix?

[BillyONeal]

@JoaoAVDuarte That is not something vcpkg can fix: only one of those libraries can be in use at a time because they both try to provide the same symbols and library names. You need to choose one.