fix(scoop-(un)hold): Correct output the messages when manifest not found, (already|not) held

[HUMORCE]

Description

• Abort hold when manifest not found
• Abort hold when app already held
• Abort unhold when app not held

Motivation and Context

Closes #5485 #5273

How Has This Been Tested?

Before:
#5485

After:

PS C:\Users\WDAGUtilityAccount> scoop hold mysql-workbench
Failed to hold 'mysql-workbench'.
PS C:\Users\WDAGUtilityAccount> scoop unhold mysql-workbench
Failed to unhold 'mysql-workbench'
PS C:\Users\WDAGUtilityAccount> scoop reset mysql-workbench
Resetting mysql-workbench (8.0.31).
Linking ~\scoop\apps\mysql-workbench\current => ~\scoop\apps\mysql-workbench\8.0.31
Creating shim for 'MySQLWorkbench'.
Creating shim for 'mysql'.
Creating shim for 'mysqldump'.
Creating shortcut for MySQLWorkbench (MySQLWorkbench.exe)
PS C:\Users\WDAGUtilityAccount> scoop hold mysql-workbench
mysql-workbench is now held and can not be updated anymore.
PS C:\Users\WDAGUtilityAccount> scoop unhold mysql-workbench
mysql-workbench is no longer held and can be updated again.

PS C:\Users\WDAGUtilityAccount> scoop hold mysql-workbench
mysql-workbench is now held and can not be updated anymore.
PS C:\Users\WDAGUtilityAccount> scoop hold mysql-workbench
'mysql-workbench' is already held.
PS C:\Users\WDAGUtilityAccount> scoop unhold mysql-workbench
mysql-workbench is no longer held and can be updated again.
PS C:\Users\WDAGUtilityAccount> scoop unhold mysql-workbench
'mysql-workbench' is not held.

Checklist:

• I have read the Contributing Guide.
• I have ensured that I am targeting the develop branch.
• I have updated the documentation accordingly.
• I have updated the tests accordingly.
• I have added an entry in the CHANGELOG.

[rashil2000]

We should use continue instead of abort. Aborting will exit the scoop process and will not proceed in case multiple apps are passed in for holding/unholding.

[HUMORCE]

Done