iter conservation efforts: save the endangered .iter() and .into_iter()

Make explicit_iter_loop and explicit_into_iter_loop allow-by-default, so
that people can turn them on if they want to enforce that style; avoid
presenting them as *the* idiomatic Rust style, rather than just *a* style.

Author: joshtriplett

clippy_lints/src/loops.rs

@@ -85,7 +85,7 @@ declare_clippy_lint! {
 /// ```
 declare_clippy_lint! {
     pub EXPLICIT_ITER_LOOP,
-    style,
+    pedantic,
     "for-looping over `_.iter()` or `_.iter_mut()` when `&_` or `&mut _` would do"
 }
 
@@ -107,7 +107,7 @@ declare_clippy_lint! {
 /// ```
 declare_clippy_lint! {
     pub EXPLICIT_INTO_ITER_LOOP,
-    style,
+    pedantic,
     "for-looping over `_.into_iter()` when `_` would do"
 }
 
@@ -1209,7 +1209,7 @@ fn lint_iter_method(cx: &LateContext<'_, '_>, args: &[Expr], arg: &Expr, method_
         cx,
         EXPLICIT_ITER_LOOP,
         arg.span,
-        "it is more idiomatic to loop over references to containers instead of using explicit \
+        "it is more concise to loop over references to containers instead of using explicit \
          iteration methods",
         "to write this more concisely, try",
         format!("&{}{}", muta, object),
@@ -1247,7 +1247,7 @@ fn check_for_loop_arg(cx: &LateContext<'_, '_>, pat: &Pat, arg: &Expr, expr: &Ex
                         cx,
                         EXPLICIT_INTO_ITER_LOOP,
                         arg.span,
-                        "it is more idiomatic to loop over containers instead of using explicit \
+                        "it is more concise to loop over containers instead of using explicit \
                          iteration methods`",
                         "to write this more concisely, try",
                         object.to_string(),