Automatically initialize Kokkos (backport)

Calling vtkm::cont::Initialize() is supposed to be optional. However, Kokkos needs to have Kokkos::initialize() called before using some devices such as HIP. To make sure that Kokkos is properly initialized, the VTK-m allocation for the Kokkos device now checks to see if Kokkos::is_initialized() is true. If it is not, then vtkm::cont::Initialize() is called.

This is a backport of !3286 (merged)

Backport: release-2.0
Backport: release-2.1

Warnings:

• Eligible for the 2.2.x branch.
• Eligible for the 2.1.x branch.

The warnings do not need to be fixed, but it is recommended to do so.

Warnings:

• Eligible for the 2.2.x branch.
• Eligible for the 2.0.x branch.

The warnings do not need to be fixed, but it is recommended to do so.

Warnings:

• Eligible for the 2.1.x branch.
• Eligible for the 2.0.x branch.

The warnings do not need to be fixed, but it is recommended to do so.

Warnings:

• Eligible for the 2.1.x branch.
• Eligible for the 2.0.x branch.

The warnings do not need to be fixed, but it is recommended to do so.

@vbolea Do you approve of this backport of !3286 (merged)?

requested review from @vbolea

Looks great!

+2

All CI errors are for defuct builds or runners that are down. See !3286 (merged) for the full CI of this change.

Do: merge

Errors:

• While processing the merge command: error occurred during merge action (@ben.boeckel @brad.king): failed to merge: duplicate target branch name: release

changed the description

I removed the backport: release since we already target release here.

Do: merge

mentioned in commit 5326fe12

mentioned in commit 135b4989

mentioned in commit 7591c46f

merged manually

mentioned in commit kmorel/vtk@2dbfbef4

mentioned in merge request vtk!11821 (merged)

mentioned in commit kmorel/vtk@57ac6758