Fix shorthand syntax error location rendering

[Abuhaithem]

Fixes #10467

Since commit 9a2e047 ("Format base *.py files at top level awscli
directory", August 2024), shorthand syntax errors have printed the literal
text {self._error_location()} instead of the input expression annotated
with a caret pointing at the parse failure:

$ aws dynamodb put-item --table-name t --item 'a=b,c==d'

Error parsing parameter '--item': Expected: ',', received: '=' for input:
{self._error_location()}

The f-string conversion in that commit left the final fragment of
ShorthandParseSyntaxError._construct_msg without the f prefix, so the
placeholder inside it was emitted verbatim. This affects every command whose
shorthand value fails to parse (--tags, --item, --attributes,
--environment, ...). The sibling DuplicateKeyInObjectError was converted
correctly and is unaffected.

This PR adds the missing f prefix, restoring the exact pre-regression
message:

Error parsing parameter '--item': Expected: ',', received: '=' for input:
a=b,c==d
      ^

Changes

• awscli/shorthand.py — move the {self._error_location()} placeholder
  into the f-string fragment (one line).
• tests/unit/test_shorthand.py — add
  test_error_message_includes_error_location, parametrized over a
  mid-string syntax error, an EOF syntax error, and the duplicate-key error.
  Each case asserts the complete message, including the caret position. The
  pre-existing test_error_parsing only asserts the exception type, which
  is the coverage gap that allowed this to regress silently; these cases
  close it for both shorthand error types.
• .changes/next-release/bugfix-shorthand-error-location.json — changelog
  entry.

Testing

Per CONTRIBUTING.md, the bug fix includes tests:

• tests/unit/test_shorthand.py: 117 passed (includes the 3 new regression
  cases)
• tests/unit/test_argprocess.py: 65 passed (shorthand error surfacing
  through ParamError)
• Verified end-to-end through bin/aws that the caret diagnostic is
  restored (no credentials required; parsing fails client-side)

No parsing behavior changes; only the error-message string on an
error-only path is affected. The restored text is identical to the output
of all releases prior to August 2024.

This pull request was generated with the assistance of AI tooling and
reviewed by Abuhaithem, per the repository's Automated Tools contribution
guidelines.

[ashovlin]

Just one comment on the changelog entry, the actual change looks good.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.64%. Comparing base (70d3b38) to head (8acd193).
⚠️ Report is 111 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop   #10468      +/-   ##
===========================================
+ Coverage    93.42%   93.64%   +0.21%     
===========================================
  Files          211      212       +1     
  Lines        17312    17362      +50     
===========================================
+ Hits         16174    16258      +84     
+ Misses        1138     1104      -34     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.