Remove @SuppressWarnings and optimize imports on Category View

[arnoudhgz]

Description

Two @SuppressWarnings could be removed by splitting up the execute
method by moving logic to separate private methods.

Also the imports of this file are improved.

Manual testing scenarios

1. Visit any category page, output should not be changed compared to before this change

Contribution checklist

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• All automated tests passed successfully (all builds on Travis CI are green)

[m2-assistant]

Hi @arnoudhgz. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

• @magento-engcom-team give me test instance - deploy test instance based on PR changes
• @magento-engcom-team give me 2.3-develop instance - deploy vanilla Magento instance

For more details, please, review the Magento Contributor Assistant documentation

[rogyar]

Hi @arnoudhgz. Thank you for the refactoring. Please note that the unit tests should be adjusted correspondingly

[arnoudhgz]

@rogyar thank you for your feedback, I have overlooked this.. Will look into it asap

[arnoudhgz]

@rogyar should I also look into the Codacy thing? It is actually not a new issue.

[orlangur]

@arnoudhgz Codacy can be safely ignored in general (and I don't see what could be a better name here particularly).

[magento-engcom-team]

Hi @orlangur, thank you for the review.
ENGCOM-4818 has been created to process this Pull Request

[VasylShvorak]

✔️ QA passed

[m2-assistant]

Hi @arnoudhgz, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.