[googletest] move link from GH to LCG

[ferdymercury]

There was a git clone failure in https://github.com/root-project/root/actions/runs/24842375265/job/72719759507?pr=22031

so maybe using LCG is more stable and more symmetric with other builtins

[github-actions]

Test Results

    22 files      22 suites   3d 9h 18m 55s ⏱️
 3 850 tests  3 849 ✅  1 💤 0 ❌
76 910 runs  76 892 ✅ 18 💤 0 ❌

Results for commit 6a8d6a8.

[guitargeek]

It doesn't feel nice to have a version regression here. I'll request a newer gtest version on LCG, and let you know once it's there.

[dpiparo]

thanks.

[dpiparo]

/backport to 6.40

[root-project-bot]

This PR has been backported to branch 6.40: #22038

[hahnjo]

So in the end, this did change the version from 1.17.0 to 1.16.0 (I had local build errors because of this)

[guitargeek]

1.17.0 is now available on LCG (or should be after next builds).

[ferdymercury]

I thought that both 1.16 or 1.17 would be fine because we have just above:

find_package(GTest 1.10 REQUIRED)

and the CI looked green.

(I had local build errors because of this)

Should we bump
find_package(GTest 1.10 REQUIRED)
to
find_package(GTest 1.17 REQUIRED)
once the LCG link is up?

or were those build errors due to incremental building?

[hahnjo]

(I had local build errors because of this)

or were those build errors due to incremental building?

Yes, I think it was related to incremental linking, which made me discover this PR.