RFR: 8253751: Dependencies of automatic modules are not propagated through module layers [v2]

[Alan Bateman]

> This is a corner case that arises when creating a Configuration for a child module layer. If an explicit module in the child configuration reads an automatic module in a parent configuration then it should read all automatic modules in the parent configurations. Unfortunately, this read edge wasn't created for the case that the child layer does not contain any automatic modules.

Alan Bateman has updated the pull request with a new target base due to a merge or a rebase. The incremental webrev excludes the unrelated changes brought in by the merge/rebase. The pull request contains ten additional commits since the last revision:

 - Formatting nit
 - Merge
 - Merge
 - Merge
 - Add @bug to test
 - Fixed typo in comment
 - Merge
 - Merge
 - If module reads automatic module in parent configuration then reads all automatic modules

-------------

Changes:
  - all: https://git.openjdk.java.net/jdk/pull/1391/files
  - new: https://git.openjdk.java.net/jdk/pull/1391/files/ec3c872f..1c5aa8cd

Webrevs:
 - full: https://webrevs.openjdk.java.net/?repo=jdk&pr=1391&range=01
 - incr: https://webrevs.openjdk.java.net/?repo=jdk&pr=1391&range=00-01

  Stats: 5201 lines in 88 files changed: 379 ins; 63 del; 4759 mod
  Patch: https://git.openjdk.java.net/jdk/pull/1391.diff
  Fetch: git fetch https://git.openjdk.java.net/jdk pull/1391/head:pull/1391

PR: https://git.openjdk.java.net/jdk/pull/1391