Fix and localize x-add-version messages

[vicroms]

This PR adds the following behavior changes:

• Print error message when given a non-existing port name
• Print a warning when there are uncommitted changes for a port
• Print a message when no files were updated at all
• Localize x-add-version messages

[strega-nil-ms]

minor nit

[strega-nil-ms]

Example messages:

PS C:\src\vcpkg> &"$env:HOMEPATH/projects/vcpkg-tool/build/vcpkg" x-add-version dbghelp
No files were updated for dbghelp
PS C:\src\vcpkg> &"$env:HOMEPATH/projects/vcpkg-tool/build/vcpkg" x-add-version dbghelp # modify portfile, don't modify vcpkg.json
No files were updated for dbghelp
PS C:\src\vcpkg> &"$env:HOMEPATH/projects/vcpkg-tool/build/vcpkg" x-add-version dbghelp # modify version
warning: local port files SHA is the same as version 0#2 in C:/src/vcpkg/versions/d-/dbghelp.json
-- SHA: c90a3ad39f6dc1e0558acf89de26f220d0fd0c1f
-- Did you remember to commit your changes?
***No files were updated***
PS C:\src\vcpkg> &"$env:HOMEPATH/projects/vcpkg-tool/build/vcpkg" x-add-version dbghelp
error: local changes detected for dbghelp but no changes to version or port version
version: 0#2
old SHA: c90a3ad39f6dc1e0558acf89de26f220d0fd0c1f
new SHA: 5ef14d2fb94b9e30b91e74a77c4808f7eeddb771
Did you remember to update the version or port version?
***No files were updated***
PS C:\src\vcpkg> &"$env:HOMEPATH/projects/vcpkg-tool/build/vcpkg" x-add-version dbghelp # vcpkg.json incorrect
error: couldn't load port dbghelp
PS C:\src\vcpkg> &"$env:HOMEPATH/projects/vcpkg-tool/build/vcpkg" x-add-version dbghelpasdf # non-existent port
error: port dbghelpasdf does not exist
PS C:\src\vcpkg> &"$env:HOMEPATH/projects/vcpkg-tool/build/vcpkg" x-add-version dbghelp # update version (no message)
PS C:\src\vcpkg> &"$env:HOMEPATH/projects/vcpkg-tool/build/vcpkg" x-add-version dbghelp --overwrite-version # update without updating version (no message)

Some comments:

• I don't love that we still don't print anything in the success case
• I appreciate that the non-existent port message != vcpkg.json incorrect now
• I really don't like that we don't print the actual error for parsing an incorrect vcpkg.json
• I don't see where print_success is used? it seems to be called, but I don't know when it's supposed to print?
  • I also don't really like print_success

[autoantwort]

This change resulted in a huge performance regression. vcpkg x-add-version --all now needs 25.5 seconds instead of 0.7 seconds on my machine. So it is now 36 times slower.

[BillyONeal]

Hmmm... probably because we're now doing git status a zillion times?

[autoantwort]

Probably. Running it > 1900 times is not the fastest. Maybe disable this additional check when passing --all

[ras0219-msft]

I think the fix is to run status a single time on the whole "ports" directory, then use that single output to judge each port.

[vicroms]

Should be fixed in #526