RFC: path reform

This RFC reforms the design of the `std::path` module in preparation for API
stabilization. The path API must deal with many competing demands, and the
current design handles many of them, but suffers from some significant problems
given in "Motivation" below. The RFC proposes a redesign modeled loosely on the
current API that addresses these problems while maintaining the advantages of
the current design.

*Thanks to @kballard, who helped spark some of the initial ideas over Ike's sandwiches!*

[Rendered](https://github.com/aturon/rfcs/blob/path-reform/text/0000-path-reform.md)
In our original discussion, the thought was that for `/a/b/c` `.iter()` would return `"/", "a", "b", "c"`, so collecting an iterator is semantically equivalent to taking the first component and pushing the rest of the components onto the end. I assume that's still the intention.