fix(scanner/redhatbase): support for empty release in rpm -qa

[MaineK00n]

What did you implement:

In rpm -qa, release may be empty.

When release is empty, there will be two spaces, which are rpm-qa separators.
In this case, strings.Split and strings.Fields behave differently.
Please refer to the following example.
https://go.dev/play/p/nc-MA6sPz4D

Since we expect the length to be constant (= we know which elements are empty), we should use strings.Split.

Also, regarding splitFileName, if the name part has -, the existing implementation passes it even if the filename is invalid.
So, although it is not standard rpm style, I would like to change it to accept the pattern ...<release>-<arch>.

Type of change

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

unit test

Checklist:

You don't have to satisfy all of the following.

• Write tests
• Write documentation
• Check that there aren't other open pull requests for the same issue/feature
• Format your source code by make fmt
• Pass the test by make test
• Provide verification config / commands
• Enable "Allow edits from maintainers" for this PR
• Update the messages below

Is this ready for review?: YES

Reference

[MaineK00n]

When building an rpm package normally, it is difficult to omit the Release tag, and I had difficulty reproducing the issue. Instead, I will submit the output of rpm -qa, which led to this fix.

$ rpm -qa --queryformat "%{NAME} %{EPOCHNUM} %{VERSION} %{RELEASE} %{ARCH} %{SOURCERPM}\n" --root=/broot  | grep "\-\-src.rpm"
extension-subscription-data-export-interface 1 1.0.0.33  x86_64 extension-subscription-data-export-interface-1.0.0.33--src.rpm

[shino]

🎊