[Ingest Manager] Fix incorrect hash when upgrading agent

[michalpristas]

What does this PR do?

For some weird special case when elastic-agent sha512 file contains a filename prefixed with ./
e.g:

748e927284f8eac2f5d8724f85a3be34d271b207147024906be4d254c5ff60affc51b191b7895e53bc3a1f4d1e76ef72e97c993d10b4be4804d9d6065ffefb9e  ./elastic-agent-7.11.0-SNAPSHOT-darwin-x86_64.tar.gz

elastic agent evaluates hashes incorrectly because it just trims the filename suffix. agent does not consider ./ to be part of the filename so it suspects that hash is
748e927284f8eac2f5d8724f85a3be34d271b207147024906be4d254c5ff60affc51b191b7895e53bc3a1f4d1e76ef72e97c993d10b4be4804d9d6065ffefb9e ./ instead of
748e927284f8eac2f5d8724f85a3be34d271b207147024906be4d254c5ff60affc51b191b7895e53bc3a1f4d1e76ef72e97c993d10b4be4804d9d6065ffefb9e

This PR just finds a correct line in a file and takes hash which is a fixed size string anyway without trimming suffixes.

Why is it important?

Fixes: #22306

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

[elasticmachine]

Pinging @elastic/ingest-management (Team:Ingest Management)

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Build Cause: [Pull request #22322 updated]

• Start Time: 2020-10-30T16:11:27.168+0000

• Duration: 21 min 38 sec

Test stats 🧪

Test	Results
Failed	0
Passed	1382
Skipped	6
Total	1388

[elasticmachine]

💚 Flaky test report

Tests succeeded.

Expand to view the summary

Test stats 🧪

Test	Results
Failed	0
Passed	1382
Skipped	6
Total	1388

[blakerouse]

Looks good.