Update types-and-traits.rst

I removed tihs:

      Furthermore, the behavior in release mode is under consideration by the The Rust Language Design Team and in the future overflow checking
      may be turned on by default in release builds (it is a `frequently requested change`_).

      .. `overflow-checks <https://github.com/rust-lang/rust/blob/master/src/doc/rustc/src/codegen-options/index.md#overflow-checks>`_
      .. `frequently requested change <https://lang-team.rust-lang.org/frequently-requested-changes.html#numeric-overflow-checking-should-be-on-by-default-even-in-release-mode>`_

Because it's not building and also because I don't want to reference transient information in the rules.  This is something for us as guideline writers to be concerned about and not consumers of this coding standard.

Author: rcseacord

src/coding-guidelines/types-and-traits.rst

@@ -32,11 +32,6 @@ Types and Traits
       avoiding potential silent wrap arounds.
       Nonetheless, abrupt program termination is not suitable and, therefore, turning this flag on must
       not be used as a substitute of explicit handling.
-      Furthermore, the behavior in release mode is under consideration by the The Rust Language Design Team and in the future overflow checking
-      may be turned on by default in release builds (it is a `frequently requested change`_).
-
-      .. `overflow-checks <https://github.com/rust-lang/rust/blob/master/src/doc/rustc/src/codegen-options/index.md#overflow-checks>`_
-      .. `frequently requested change <https://lang-team.rust-lang.org/frequently-requested-changes.html#numeric-overflow-checking-should-be-on-by-default-even-in-release-mode>`_
 
       Safety-critical software requires consistent and predictable behavior across all build configurations.
       Explicit handling of potential overflow conditions improves code clarity,