ID 305205 - Some archives from 2.0v1 will experience shader compile errors during version upgrade

Problem summary
Some archives from 2.0v1 and 2.0v2 will not convert correctly to Mari 3, resulting in multiple Shader Compile errors.

Customer reported version
3.3v1
Customer reported platform
linux
Steps to reproduce

1) Run Mari in verbose mode [-V]

2) Attempt to open an unconverted archive originating in Mari 2.0v1 (such as attached archive)

3) Mari will ask if you wish to convert the archive, choose 'yes'

4) Mari will return a render shader error and compile errors in the MariLog/Verbose log.

Workaround
- Try opening the project in 2.6v5 where we modified the upgrade process 
- Saving the project
- Now attempt to open the project in 3.3v1

Reproduced by support
Unable to convert 2.0v1 archive successfully in:
3.3v1, 3.2v1, 3.1v3, 3.1v1

Earliest version tested
3.0v4 works

Expected behaviour
We should be able to convert archives without needing to save at incremental versions. 

Actual behaviour
Unfortunately, some archives may experience shader compile errors when using problematic nodes i.e. MRI_Layer_MergeNoAlpha, which doesn't match its current ID in version 3 and up: MRI_Layer_MergeNoAlpha_v2

Most users do not run into this issue as they are likely to have upgraded Mari version gradually after each release.