Package conflict errors are thrown when both Magic Leap and Windows MR loaders are downloaded and added to XR Plugin Management. Refer to the attached screenshots.

Steps to reproduce:
1) Download support for Magic leap
2) Create a new project
3) Windows > Package Manager
4) Install Magic leap.
5) Edit > Project Settings > XR Plugin Management
6) Add both loaders Windows MR and Magic Leap

Actual result: Package conflict errors are thrown when both Magic Leap and Windows MR loaders are added

Expected Result: No errors should be thrown in the console when loaders are added to XR plugin management

Occurring on Unity version: 2020.1.0a14, 2019.3.0f1

Occurring On Package version: 3.0.4, 3.0.3, 3.0.0

Note: Magic Leap was added to XR Plugin Management from 3.0.0

Environment: Both Windows and Mac

Stack trace:

GUID [c11fc303a09ebe544abdcd0597fad10a] for asset 'Packages/com.unity.xr.magicleap/Tests/Runtime/Resources/TestSetup' conflicts with:
'Packages/com.unity.xr.windowsmr/Tests/Runtime/Resources/TestSetup' (current owner)
We can't assign a new GUID because the asset is in an immutable folder. The asset will be ignored.