Add workflow for testing against Trilinos develop

[ppraegla]

Description and Context

Adds a workflow that builds the Docker image with the Trilinos develop version, builds 4C, and runs the tests.
This is a draft for now because

1. the build fails (something with arborX) and
2. the workflow schedule is not finalized yet. Ideally, I would like to run this workflow weekly and allow the option to run the workflow manually for specific commit SHAs. However, I have not yet found a nice way to add the manual trigger without duplicating the jobs.

@maxfirmbach , @eulovi (I added you to my fork. So you can directly push to my branch. Hopefully, this works)

Related Issues and Merge Requests

#288, #291, #290

[maxfirmbach]

Yeah ArborX throws warnings most likely, due to it being a quite old version compared to Kokkos ... I currently don't have the time to look into this in detail though ...

[ppraegla]

@maxfirmbach Should we wait with this PR until we update ArborX? In #290, you said you want to wait until the next official ArborX release. I'm hesitant to add a workflow now that will immediately fail.

[maxfirmbach]

@maxfirmbach Should we wait with this PR until we update ArborX? In #290, you said you want to wait until the next official ArborX release. I'm hesitant to add a workflow now that will immediately fail.

@ppraegla That's fine for me 👍.

[aprokop]

Yeah ArborX throws warnings most likely, due to it being a quite old version compared to Kokkos ... I currently don't have the time to look into this in detail though ...

Hi, ArborX developer here. This has been fixed fixed upstream in arborx/ArborX#1183.

Next ArborX release should happen within a month. Functionally, it's all there, but currently going through some performance regression testing and minor API tweaking.

[maxfirmbach]

Yeah ArborX throws warnings most likely, due to it being a quite old version compared to Kokkos ... I currently don't have the time to look into this in detail though ...

Hi, ArborX developer here. This has been fixed fixed upstream in arborx/ArborX#1183.

Next ArborX release should happen within a month. Functionally, it's all there, but currently going through some performance regression testing and minor API tweaking.

Great 👍 Maybe @isteinbrecher and me have a look at the changes made to ArborX soonish.

[isteinbrecher]

Thanks @aprokop for letting us know! Yes, @maxfirmbach lets have a look at the changes in the next weeks.

[mayrmt]

@maxfirmbach @isteinbrecher what's the status here?

[maxfirmbach]

@maxfirmbach @isteinbrecher what's the status here?

No update yet, need to fix the ArborX related problems first.