fix a JIT bug related to inlined structure constructors

Merge to v5.3.4
(cherry picked from commit fd883dbf32a1635c28d3e6e4553f2dd1fd60bdb7)
update for 5.3.4
(cherry picked from commit 0d3ae8b2e3586e5c7a733a68a859dcf8c385f9c8)
fix jump-to-defining-file when a stacktrace window is open
(cherry picked from commit 951538ab90cf39b56c4a5539eb9e766000ff4a44)
raco dist: update ELF section when adjusting data size

Merge to v5.3.4
(cherry picked from commit f450e50354fcf70a71d22621c958508b8f438766)
raco pkg: GitHub API now requires a User-Agent

Merge to v5.3.4
(cherry picked from commit 9d43fcad3e5fb22146cb4435172b26571987bda0)
racket/draw: fix `in-region?' method of `region%'

Merge to v5.3.4
(cherry picked from commit 917ec51eeebcfe2e2a0057787cd3768b96df1fdb)
fix bytecode compiler safefor-space, tigher bytecode validation

The safe-for-space pass could add clearing operations on "typed"
stack positions, which are known to contain a fixnum, flonum, or
extflonum. Non-clearing references, however, were not annotated to
indicate that clearing references were present, since clearing is
not expected on typed positions.

Along the lines of not expecting clearing, the bytecode validator's
encoding of the stack doesn't accomodate both "has a type" and "claims
never to be cleared", so it couldn't detect the bytecode compiler
bug. (Also, this problem didn't show up in the HOSC paper's model of
the validator, because the model pre-dates type tracking.)

Fix the bytecode compiler's space-safety pass so that it never inserts
clearing operations for typed stack positions. Then, the validator can
simply reject any attempt to clear a typed position.

Also, annotate applications generated by lifting as safe-for-space
tail calls.

Merge to v5.3.4
(cherry picked from commit 7ad1ddab64afbb58f02d8d1b28b55c05d015aea0)

Conflicts:
	src/racket/src/cstartup.inc
	src/racket/src/schvers.h
fix version number and cstartup.inc for compiler change in prev commit