Limit Github Actions runtime and cleanup always

[uvatbc]

https://issues.apache.org/jira/browse/SOLR-XXXXX

Description

The Solr tests ran for over 2 days - and I forgot to check them over the weekend.
Keeping a 96 core machine running for that long is expensive.

Solution

1. Limit the runtime to 90 minutes
2. At the end, always send a clear kill signal to the job running in Crave

Tests

None: This is a Github Actions change

Checklist

Please review the following and check all that apply:

• I have reviewed the guidelines for How to Contribute and my code conforms to the standards described there to the best of my ability.
• I have created a Jira issue and added the issue ID to my pull request title.
• I have given Solr maintainers access to contribute to my PR branch. (optional but recommended, not available for branches on forks living under an organisation)
• I have developed this patch against the main branch.
• I have run ./gradlew check.
• I have added tests for my changes.
• I have added documentation for the Reference Guide

[HoustonPutman]

I changed it to 40 min, because if everything is working it runs in like 20 min.

[dsmiley]

Thanks!