typesafe_array_init rule reports violations as though they were of the array_init rule.

[mildm8nnered]

New Issue Checklist

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

Describe the bug

The TypesafeArrayInitRule outsources some of its functionality to the ArrayInitRule. The violations are reported as being of array_init rather than typesafe_array_init.

Complete output when running SwiftLint, including the stack trace and command used

typesafe_array_init is an analyzer rule, so it's hard to run the analyzer on it in isolation, but the following unit test illustrates the problem:

final class TypesafeArrayInitRuleTests: SwiftLintTestCase {
    func testViolationRuleIdentifier() {
        let baseDescription = TypesafeArrayInitRule.description
        guard let triggeringExample = baseDescription.triggeringExamples.first else {
            XCTFail("No triggering examples found")
            return
        }
        guard let config = makeConfig(nil, baseDescription.identifier) else {
            XCTFail("Failed to create configuration")
            return
        }
        let violations = SwiftLintFrameworkTests.violations(triggeringExample, config: config, requiresFileOnDisk: true)
        XCTAssertGreaterThanOrEqual(violations.count, 1)
        XCTAssertEqual(violations.first?.ruleIdentifier, baseDescription.identifier)
    }
}

This will fail the final check, as the types of the violations will not be typesafe_array_init

[mildm8nnered]

Resolved by #5710