create gitlab test for libyogrt

Nobody has claimed this yet.

We should also add a gitlab test for libyogrt. Something like:

1) submit a job with a 5 minute time limit
2) check that a call to libyogrt returns a remaining time value that is 5 minutes or less
3) wait ~30 seconds, call libyogrt again and check that time remaining has decreased by something close to 30 seconds

We'd want tests for both SLURM and LSF.

Ideally, we should test all of:
1) our existing system installs
2) spack install of libyogrt, e.g., ``spack install libyogrt scheduler=slurm``
3) autotools install of libyogrt

For an example code that calls libyogrt:
```
# install libyogrt from spack
bin/spack install libyogrt

# test program
>>: cat grt.c
#include
#include
#include "yogrt.h"
int main (int argc, char* argv[])
{
long int secs = yogrt_remaining();
printf("%lu\n", secs);
return 0;
}

# allocate a node in pdebug, which has an hour time limit
salloc -N1 -ppdebug

# try spack install
yogrtdir=/path/to/libyogrt/spack/install/lib
gcc -o grt grt.c -L${yogrtdir} -Wl,-rpath,${yogrtdir} -lyogrt
./grt
2147483647

# try again with system install of libyogrt
yogrtdir=/usr/lib64
gcc -o grt grt.c -L${yogrtdir} -Wl,-rpath,${yogrtdir} -lyogrt
./grt
3547
```

Start by examining the existing libyogrt tests and the grt.c example described in the issue. Determine how tests are run for SLURM and LSF, then cover system, Spack, and autotools installs. Done means verifying remaining time decreases as expected for both schedulers and installation methods.

Written by the indexing model from the issue text.