throwDecode doesn't have HasCallStack

though `throwM` does.

So the backtraces collected by exceptions end somewhere inside `aeson` library, not including the call-site of `throwDecode`:

```
*Data.Aeson> :m +Control.Exception
*Data.Aeson Control.Exception> :set -XOverloadedStrings
*Data.Aeson Control.Exception> throwIO (AesonException "wrong")
*** Exception: aeson: wrong

HasCallStack backtrace:
throwIO, called at :3:1 in interactive:Ghci1

*Data.Aeson Control.Exception> throwDecode "nll" :: IO Int
*** Exception: aeson: Unexpected "nll", expecting JSON value

HasCallStack backtrace:
throwIO, called at libraries/exceptions/src/Control/Monad/Catch.hs:343:12 in exceptions-0.10.11-97e4:Control.Monad.Catch
throwM, called at src/Data/Aeson/Decoding.hs:89:61 in aeson-2.3.1.0-inplace:Data.Aeson.Decoding

```

Start with the throwDecode entry point in src/Data/Aeson/Decoding.hs around line 89, and compare its exception handling with throwM. Reproduce the shown throwDecode example, then verify that the resulting HasCallStack backtrace includes the caller rather than ending inside aeson.

Written by the indexing model from the issue text.