Report txt: fix printing of non-ascii details

[pirat89]

Previous commit introduced couple of issues regarding details of reports that could lead to situations like:

• remediation instructions has not been printed when non-ascii characters have been present
• possible unwanted empty line when remediation has been specified but relative symlinks hasn't
• if the URL title contained non-ascii character, it has been broken too (on py2)

This should handle all mentioned problems when generating the txt file.

[github-actions]

Thank you for contributing to the Leapp project!

Please note that every PR needs to comply with the Leapp Guidelines and must pass all tests in order to be mergeable.
If you want to request a review or rebuild a package in copr, you can use following commands as a comment:

• review please @oamg/developers to notify leapp developers of the review request
• /packit copr-build to submit a public copr build using packit

To launch regression testing public members of oamg organization can leave the following comment:

• /rerun to schedule basic regression tests using this pr build and leapp-repository*master* as artifacts
• /rerun 42 to schedule basic regression tests using this pr build and leapp-repository*PR42* as artifacts
• /rerun-sst to schedule sst tests using this pr build and leapp-repository*master* as artifacts
• /rerun-sst 42 to schedule sst tests using this pr build and leapp-repository*PR42* as artifacts

Please open ticket in case you experience technical problem with the CI. (RH internal only)

Note: In case there are problems with tests not being triggered automatically on new PR/commit or pending for a long time, please consider rerunning the CI by commenting leapp-ci build (might require several comments). If the problem persists, contact leapp-infra.

[pirat89]

/rerun

[github-actions]

Copr build succeeded: https://copr.fedorainfracloud.org/coprs/build/6516691

[github-actions]

Testing Farm request for RHEL-8.6-rhui/6513877;6516691 regression testing has been created.
Once finished, results should be available here.
Full pipeline log.

[github-actions]

Testing Farm request for RHEL-7.9-rhui/6513877;6516691 regression testing has been created.
Once finished, results should be available here.
Full pipeline log.

[pirat89]

@oamg/developers

tested manual on RHEL 7 & RHEL 8:

----------------------------------------
Risk Factor: high
Title: [snip]
Summary: [snip]
Related links:
    - Difference in Python versions and support in RHEL 8: https://red.ht/rhel-8-python
    - kurník řepa: https://red.ht/rhel-8-python
Remediation: [hint] Please run "alternatives --set pythořn /usr/bin/python3" after upgra%čde
Key: 0c98585b1d8d252eb540bf61560094f3495351f5

Risk Factor: high (inhibitor)
Title: Upgrade requires links in root directory to be relative
Summary: After rebooting, parts of the upgrade process can fail if symbolic links in / point to absolute paths.
Please change these links to relative ones.
Remediation: [command] sh -c ln -snf bořek /bořislav && ln -snf root/tlučhuba /kuřislav
Key: 3d895ad37ceaf4157864d439edb6bd75562061fa

(yes, these invalid commands etc is the change I wanted, so the output looks like it should)

[pirat89]

Note there are no any unit-tests for this and I am skipping to add them now to unblock upstream testing of upgrades.

[PeterMocary]

LGTM!

• - remediation gets printed even with non-ascii characters
• - unwanted empty line is no longer present when external links aren't specified
• - link with non-ascii characters gets printed just fine

Tested on RHEL8 and RHEL7 as follows:

Risk Factor: high (inhibitor)
Title: Local repository detected
Summary: The following local repository has been found: my-repo (their baseurl starts with file:///). Currently leapp does not support this option.
Related links:
    - Customizing your Red Hat Enterprise Linux in-place upgrade ľščťžýáíéôúäň: ľščťžýáíéôúäň https://red.ht/ipu-customisation-repos-known-issues
Remediation: [hint] By using Apache HTTP Server you can expose your local repository via http. See the linked article for details. ľščťžýáíéôúäň
Key: 3450b32bfad8e1837b73b18e56c556d1052d5e4b
----------------------------------------
Risk Factor: high
Title: Remote root logins globally allowed using password
Summary: RHEL9 no longer allows remote root logins, but the server configuration explicitly overrides this default. The configuration file will not be updated and root is still going to be allowed to login with password. This is not recommended and considered as a security risk.
Remediation: [hint] If you depend on remote root logins using passwords, consider setting up a different user for remote administration. Otherwise you can ignore this message.
Key: e738f78bc8f3a84411a4210e3b609057139d1855