Rule Request: no-print

New Issue Checklist

• Updated SwiftLint to the latest version
• I searched for existing GitHub issues

New rule request

1. Why should this rule be added? Share links to existing discussion about what
   the community thinks about this.

Leftover logs in production can cause security breaches in any app. Also, logging to the console has performance drawbacks on iOS.

2. Provide several examples of what would and wouldn't trigger violations.

Any calls to print, debugPrint or dump would trigger a warning violation.

3. Should the rule be configurable, if so what parameters should be configurable?

I cannot think of anything that should be configurable at this moment.

4. Should the rule be opt-in or enabled by default? Why?
   See README.md for guidelines on when to mark a rule as opt-in.

Considering how it could pose as a security violation, I do believe no-print should be enabled by default.

If this RFC is approved, I'm more than happy to work on it and open a PR.

Start with the repository's README.md opt-in-rules guidance and review how existing SwiftLint rules are organized. Define completion around detecting calls to print, debugPrint, and dump without configuration, then add coverage for triggering and non-triggering examples in the rule's tests.