Use int type name consistently (#10579)

# Description
When referring to the type use `int` consistently. Only when referring
to the concept of integer numbers use `integer`.

- Fix `random integer` to `random int` tests
  - Forgot in #10520
- Use int instead of integer in error messages
- Use int type name in bits commands
- Fix messages in `for` examples
- Use int typename in `into` commands
- Use int typename in rest of commands
- Report errors in `nu-protocol` with int typename

Work for #10332 

# User-Facing Changes
User errorrs should now use `int` so you can easily find the necessary
commands or type annotations.

# Tests + Formatting
Only two tests found that needed updating

crates/nu-command/src/math/utils.rs

@@ -108,7 +108,7 @@ pub fn calculate(
         PipelineData::Value(val, ..) => mf(&[val], span, name),
         PipelineData::Empty { .. } => Err(ShellError::PipelineEmpty { dst_span: name }),
         val => Err(ShellError::UnsupportedInput(
-            "Only integers, floats, lists, records or ranges are supported".into(),
+            "Only ints, floats, lists, records, or ranges are supported".into(),
             "value originates from here".into(),
             name,
             // This requires both the ListStream and Empty match arms to be above it.

crates/nu-command/src/math/variance.rs

@@ -66,8 +66,7 @@ fn sum_of_squares(values: &[Value], span: Span) -> Result<Value, ShellError> {
             Value::Int { .. } | Value::Float { .. } => Ok(value),
             Value::Error { error, .. } => Err(*error.clone()),
             _ => Err(ShellError::UnsupportedInput(
-                "Attempted to compute the sum of squares of a non-integer, non-float value"
-                    .to_string(),
+                "Attempted to compute the sum of squares of a non-int, non-float value".to_string(),
                 "value originates from here".into(),
                 span,
                 value.span(),