unwrap ExceptionStack in code_ handling

[vchuravy]

We inform users to use:

Catch this exception as `err` and call `code_typed(err; interactive = true)`

But in the REPL this is often not useful advice since the exception of interest is actually wrapped...
This biggest issue with this PR is that we are technically committing type-piracy, but this improves the UX for working with compiler errors from GPUCompiler a lot.

I think there is a second error type that we can get which is when the error happens in a file that is being include'd

[codecov]

Codecov Report

❌ Patch coverage is 0% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 0.00%. Comparing base (47da204) to head (f265ca2).

Files with missing lines	Patch %	Lines
src/reflection.jl	0.00%	3 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #737       +/-   ##
==========================================
- Coverage   75.07%   0.00%   -75.08%     
==========================================
  Files          24      24               
  Lines        3639    3562       -77     
==========================================
- Hits         2732       0     -2732     
- Misses        907    3562     +2655     

☔ View full report in Codecov by Sentry.
📢 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.

[maleadt]

Catch this exception as `err` and call `code_typed(err; interactive = true)`

I never was a big fan of this; @device_code_typed is always the tool I use. But for large applications I guess it may be useful.

[vchuravy]

cc: @giordano since it came up in conversation