Tracking issue for `path_components_peek` stabilization

[aturon]

The path::Components::peek method allows you to peek at the next component in the iterator without actually consuming it. There's no strong reason for it to remain unstable, except that the conventions around such methods are a bit unclear.

[nagisa]

Any reason a more general Peekable<Components> cannot be used instead?

[aturon]

@nagisa Not really, no.

Nominating for deprecation in 1.6.

[alexcrichton]

🔔 This issue is now entering its cycle-long final comment period for deprecation 🔔

[alexcrichton]

The libs team discussed this during triage today and the decision was to deprecate