[Ubuntu] do not wrap apt-fast in mock script

[mikhailkoliada]

Description

We are wrapping up multiple apt tools into a mock retries script tp avoid race condition caused by apt during images generation. While it works for the most of the tools, for apt-fast it is not, because we are referencing the /usr/bin tools into the /usr/local/bin directory. apt-fast is not the official deb-based bistro tool and never belonged to the /usr/bin directory (not to say that apt-mocking this tool is pointless as it is not being used during images generation).

Previously, apt-fast has been installed into the /usr/local/sbin directory, but since recently, upstream has changed its installation destination to the /usr/local/bin one, in turn, we are cleaning up the /usr/local/bin/apt-fast file in our cleanup.sh script, as we expect it to be a mock alternative of the actual tool, but in reality we are removing the tool from the image entirely. We should not wrap apt-fast anyhow so I propose we stop doing this.

Related issue: #9780

Check list

• Related issue / work item is attached
• Tests are written (if applicable)
• Documentation is updated (if applicable)
• Changes are tested and related VM images are successfully generated

[mikhailkoliada]

/azp run ubuntu2004,ubuntu2204

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).