CompatHelper: bump compat for VectorInterface to 0.5 for package NDTensors, (keep existing compat)

[github-actions]

This pull request changes the compat entry for the VectorInterface package from 0.4.2 to 0.4.2, 0.5 for package NDTensors.
This keeps the compat entries for earlier versions.

Note: I have not tested your package with this new compat entry.
It is your responsibility to make sure that your package tests pass before you merge this pull request.

[mtfishman]

@lkdvos it looks like this may have broken a certain contraction pattern in TensorOperations, I see a failure in this test: https://github.com/ITensor/ITensors.jl/blob/v0.7.3/NDTensors/src/lib/TensorAlgebra/test/test_basics.jl#L163-L165 where we are looping over a number of tensor contraction patterns.

[mtfishman]

I'm having trouble reproducing it with a minimal example.

[lkdvos]

From what I can see here, this should not related to the compat entry, and really is a bug that probably existed before. I'll have a look in a second

[lkdvos]

I see what happened: somehow there is a compat problem, and the installed version of TensorOperations in the failing tests is 0.7.1, which is incredibly outdated. I am not entirely sure why this is happening, as this should probably be excluded by the compat entry of the packages here, since the order of arguments changed.

I guess this is because you don't have TensorOperations as a dependency, and thus don't have a compat entry for it?

[lkdvos]

As a sidenote, this problem should resolve itself as soon as the tests automatically take the new registered version of TensorOperations, JuliaRegistries/General#119490

[mtfishman]

I see what happened: somehow there is a compat problem, and the installed version of TensorOperations in the failing tests is 0.7.1, which is incredibly outdated. I am not entirely sure why this is happening, as this should probably be excluded by the compat entry of the packages here, since the order of arguments changed.

I guess this is because you don't have TensorOperations as a dependency, and thus don't have a compat entry for it?

I see, that would explain it. Thanks for investigating. Yeah, TensorOperations is just being used for testing right now but I guess we could put a compat entry in test/Project.toml.

[mtfishman]

As a sidenote, this problem should resolve itself as soon as the tests automatically take the new registered version of TensorOperations, JuliaRegistries/General#119490

Yes, looks like that fixed it.