Rule Request: Inverting redundant_optional_initialization

Proposal: add an "inverted" configuration option to the existing redundant_optional_initialization rule, so that initializing variables with nil is required rather than disallowed.

Also, I have found that variables declared as Optional<Type> rather than Type? are not implicitly initialized to nil. The rule as currently implemented assumes that they are, so I intend to fix that while I'm at it.

New Issue Checklist

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

New rule request

Please describe the rule idea, format
this issue's title as Rule Request: [Rule Name] and describe:

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

Inspired by this discussion in the Swift forums: https://forums.swift.org/t/prepitch-optional-variables-should-require-explicit-initialization-to-nil/26077

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

The reverse of the examples for the existing rule.

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

Setting inverted: true would treat the absence, rather than presence, of = nil as a violation.

4. Should the rule be opt-in or enabled by default? Why?

The inverted configuration should default to false to preserve existing behavior.

Start with the existing redundant_optional_initialization rule and its current examples and configuration. Check how Optional declarations are handled, then define the inverted setting so omission or presence of = nil is diagnosed as intended while preserving the default behavior; verify both cases with the rule's tests.