Use the 'Location:' header only for latest FTL tag API check.

[dschaper]

By submitting this pull request, I confirm the following:
please fill any appropriate checkboxes, e.g: [X]

• I have read and understood the contributors guide, as well as this entire template.
• I have made only one major change in my proposed changes.
• I have commented my proposed changes within the code.
• I have tested my proposed changes, and have included unit tests where possible.
• I am willing to help maintain this change if there are issues with it later.
• I give this submission freely and claim no ownership.
• It is compatible with the EUPL 1.2 license
• I have squashed any insignificant commits. (git rebase)

---

What does this PR aim to accomplish?:

Fixes #3986

GitHub API headers now have CSP with the work "location" in the policy. FTL tags came back with that location as the tag.

dan@raspberrypi:~ $ curl -sI https://github.com/pi-hole/FTL/releases/latest | grep --color=never -i Location | awk -F / '{print $NF}' | tr -d '[:cntrl:]'
v5.3.4socket-worker-5029ae85.jsd

How does this PR accomplish the above?:

Only use Locaition: which should only grab the proper header.

dan@raspberrypi:~ $ curl -sI https://github.com/pi-hole/FTL/releases/latest | grep --color=never -i Location: | awk -F / '{print $NF}' | tr -d '[:cntrl:]'
v5.3.4

[pralor-bot]

This pull request has been mentioned on Pi-hole Userspace. There might be relevant details there:

https://discourse.pi-hole.net/t/pi-hole-update-wird-nicht-installiert/42862/11

[pralor-bot]

This pull request has been mentioned on Pi-hole Userspace. There might be relevant details there:

https://discourse.pi-hole.net/t/ftl-keeps-updating-to-same-version/42898/2

[ArrowNemesis]

Hi dschaper, which code do I use, I'm bit confuse about the codes look too complex. pls help afap thank you.

[ArrowNemesis]

Has this issue been fixed yet?

[ArrowNemesis]

what does red and green colour indicate?

[pralor-bot]

This pull request has been mentioned on Pi-hole Userspace. There might be relevant details there:

https://discourse.pi-hole.net/t/pihole-c-causes-pihole-ftl-log-errors-ftl-v5-3-4/42154/28