EscapeUtils: add test cases and an assert for addresses escaping to to a closure

[eeckstein]

It's essential that a non-escaping closure will be treated as having a relevant type for escape analysis. Because if it's capturing an (inout) address it's like it's storing a pointer to the captured variable in its context.

Adds test cases for rdar://105676825

[eeckstein]

@swift-ci smoke test

[finagolfin]

@eeckstein, it appears this new case breaks a test on the Android armv7 CI and probably other 32-bit platforms like watchOS too:

Command Output (stderr):
--
SIL verification failed: struct operand type does not match field type
  $Builtin.Int64
  $Builtin.Int32
Verifying instruction:
     %1 = integer_literal $Builtin.Int64, 0       // user: %2
->   %2 = struct $Int (%1 : $Builtin.Int64)       // user: %5
     store %2 to %0 : $*Int                       // id: %5
In function:
// test_closure_capturing_address

These 32-bit platforms are probably not that important anymore, but if you know a quick fix, please let me know.

[eeckstein]

@buttaface Thanks! This should fix it: #63932