Redex: fix a small bug in the list-machine example
Avoid doing the 2nd pass twice at the top-level

Thanks to Eric for pointing this out.
Add examples for `for/lists`
Fix regression for (begin) and simplify
Fixed in-generator's handling of arity zero.

Also combined expansion of in-generator for both expression and sequence
contexts, and made a number of places that were handling arity dynamically
to handle it statically instead.
Fixed collects/meta/props so that `props verify' runs without error.
fix docs for redex-generator
Gave collects/meta/check-dists more time when run by DrDr.
Set drdr:random property for files with nondeterministic output.

- src/build/make-install: nondeterministic job order
- src/build/make: nondeterministic job order
- src/build/configure: "checking for x86 cpuid 1 output... " line varies
- collects/tests/zo-size.rkt: file sizes
- collects/tests/unstable/temp-c/ttt-players.rkt: random
- collects/tests/unstable/temp-c/ttt-bench.rkt: timing
- collects/tests/unstable/temp-c/id-bench.rkt: timing
- collects/tests/unstable/temp-c/bench.rkt: timing
- collects/tests/unstable/temp-c/bench-affine.rkt: timing
- collects/tests/typed-racket/tr-random-testing.rkt: random
- collects/tests/racket/will.rktl: current-memory-use
- collects/tests/racket/threadlib.rktl: nondeterministic threads
- collects/tests/racket/syntax-tests.rktl: file-or-directory-modify-seconds
- collects/tests/racket/subprocess.rktl: process ids
- collects/tests/racket/submodule.rktl: temporary file names
- collects/tests/racket/stx.rktl: temporary file names
- collects/tests/racket/structlib.rktl: current-seconds
- collects/tests/racket/stress/vector.rkt: timing
- collects/tests/racket/stress/sequence.rkt: timing
- collects/tests/racket/stress/mpfr-ffi-call-vs-racket.rkt: timing
- collects/tests/racket/stress/module-stack.rkt: vector-set-performance-stats!
- collects/tests/racket/stress/hash.rkt: timing
- collects/tests/racket/stress/fuzz.rkt: random
- collects/tests/racket/stress/dict.rkt: timing
- collects/tests/racket/stress/apply.rkt: timing
- collects/tests/racket/sp.rktl: process ids
- collects/tests/racket/setup.rktl: temporary file names
- collects/tests/racket/serialize.rktl: current-seconds and temporary file names
- collects/tests/racket/sequence.rktl: random
- collects/tests/racket/runaway-place.rkt: nondeterministic output interleaving
- collects/tests/racket/resource.rktl: temporary file names
- collects/tests/racket/prompt-sfs.rkt: current-memory-use and dump-memory-stats
- collects/tests/racket/place-channel.rkt: nondeterministic places
- collects/tests/racket/place-channel-socket.rkt: unpredictable port number
- collects/tests/racket/place-channel-fd.rkt: unpredictable port number
- collects/tests/racket/parallel-build.rkt: temporary file names
- collects/tests/racket/package-gen.rktl: random
- collects/tests/racket/pack.rktl: temporary file names
- collects/tests/racket/module.rktl: temporary file names
- collects/tests/racket/iostream.rktl: timing
- collects/tests/racket/format.rkt: random
- collects/tests/racket/foreign-test.rktl: pointer addresses
- collects/tests/racket/fixnum.rktl: random
- collects/tests/racket/date.rktl: current-seconds
- collects/tests/racket/cm.rktl: file-or-directory-modify-seconds
- collects/tests/racket/benchmarks/shootout/chameneos.rkt: nondeterministic threads
- collects/tests/racket/benchmarks/shootout/auto.rkt: timing
- collects/tests/racket/benchmarks/rx/auto.rkt: timing
- collects/tests/racket/benchmarks/common/auto.rkt: timing
- collects/tests/racket/basic.rktl: random
- collects/tests/planet/run-all.rkt: nondeterministic job order
- collects/tests/openssl/basic.rkt: nondeterministic threads
- collects/tests/net/stress/websocket.rkt: timing
- collects/tests/gracket/draw-mem.rkt: current-memory-use
- collects/tests/future/timing-test.rkt: timing
- collects/tests/future/random-future.rkt: random
- collects/tests/frtime/time.rkt: seconds
- collects/tests/drracket/example-tool.rkt: temporary file names
- collects/redex/tests/ryr-test.rkt: temporary file names
- collects/redex/examples/delim-cont/randomized-tests.rkt: random
- collects/math/tests/bigfloat-custodian.rkt: random
- collects/2htdp/tests/struct-universe.rkt: nondeterministic parallel worlds
Fixed problems with collects/meta/props.

- combined drdr:random properties for collects/tests/racket/stress
- removed properties for src/build/{make,make-install,configure}
Clean up unit tests

Remove #; comments because they break paredit. Enable some
commented tests that should pass.
fix srcloc-missing-from-exn bug in struct/dc
fix call-with-transaction error (disconnected rollback)

Also, clarify in docs that break causes disconnect.
Synch German string constants with latest.
Fix racket/draw doc typo
Fix parsing of (Struct ...) types.

This was a regression that appeared in 5.3.1
Adjusted check syntax to properly deal with different identifiers
that have overlapping ranges in the editor; also got rid of the
id-set stuff

Getting rid of the id-set information that was computed means that now
the mouse-over green bubbles, the "jump to next binding occurrence"/
"jump to bound occurrence" keybindings/menu items, and the renaming
are all being computed from the arrows information as needed, instead
of building up sets as check syntax collects information. This may
change the way Check Syntax behaves in some cases; so far the only
example I've found has been strange and are arguably for the
better. Specifically, this program

  (define-syntax-rule (m x) (λ (x) x)) (m z)

no longer draws a green bubble when you mouse over the "z", since
there are no arrows (the only arrow that might have been drawn is
discarded since its start and end points are the same place).

This speeds up the "analyze the expanded code" phase of check syntax,
making it approximately 1.6x faster than before (going from about 31
seconds to about 19 seconds for this phase for the
drracket/private/unit.rkt file (on my machine)). Also, the replay
phase is probably a bit faster now, tho, too: there were 1.07x fewer
elements to process in the trace that comes back from online check
syntax now for that same file (33063 to 30842)

Note that this is only that one phase: this doesn't count the time to
actually expand the program (the dark blue bubble phase) nor the time
to send the results between places, nor the time to replay the
collected information (the light purple bubble phase).
should have been part of 299063d
automate some overlapping identifier tests
dont draw the lime green bubbles for imported identifiers

One problem with commit 299063d7c154428d000eb436aae4320b5781b15b
is that the new method for computing the lime green arrows no
longer has the information necessary to distinguish different
identifiers that come from the same require.

This means that, before this commit, mousing over an imported
identifier can be a real interactivity killer. So, instead of
adding more information to distinguish those ids, lets just
try not draw the lime green bubbles for imported identifiers
and see how that feels