Deprecate and remove impl From<NonZeroU32> for Error.

[briansmith]

The From<NonZeroU32> for Error implementation doesn't do any checking of its inputs; for example, it doesn't verify that an "internal" error code isn't being used, nor does it verify that any internal error code is actually a valid/known one.

I propose:

• Replace all internal uses of it; See Enforce OS errors are in the allowed range. #441 for some progress here.
• Add pub const fn Error::new_custom(value: u16) -> Error
• Add pub const fn Error::new_os(u32) -> Error with range checking, as done in Enforce OS errors are in the allowed range. #441, though Enforce OS errors are in the allowed range. #441 doesn't make it pub.
• Mark the impl From<NonZeroU32> for Error as #[deprecated] now.
• In a future SemVer-breaking release, remove the implementation.

This way, internal errors will eventually only be able to be constructed from within the crate.

[josephlr]

I like this idea, having something like:

impl Error {
  pub const fn from_os_error(i32) -> Self;
  pub const fn raw_os_error(self) -> Option<i32>

  pub const fn new_custom(u16) -> Self;
  const fn new_internal(u16) -> Self;
}

seems reasonable to me. We may want to use i32 consistently for OS errors as that's what libstd uses (and it's the return type of errno).

EDIT: Should we also remove the Error::code method?