Select Analysis: Don't recursively crawl merge subselects

[keraion]

Brief summary of the change made

Allows multiple types for BaseSegment.recursive_crawl's no_recursive_seg_type
Don't analyze merge statements that may be present in subselects for object references

• Fixes regression 3.0.5: tsql RF03 bug. INSERT must not contain table reference, $ACTION must not contain table reference #5980

Are there any other side effects of this change that we should be aware of?

None

Pull Request checklist

• Please confirm you have completed any of the necessary steps below.

• Included test cases to demonstrate any code changes, which may be one or more of the following:

  • .yml rule test cases in test/fixtures/rules/std_rule_cases.
  • .sql/.yml parser test cases in test/fixtures/dialects (note YML files can be auto generated with tox -e generate-fixture-yml).
  • Full autofix test cases in test/fixtures/linter/autofix.
  • Other.

• Added appropriate documentation for the change.

• Created GitHub issues for any relevant followup/future enhancements if appropriate.

[github-actions]

Coverage Results ✅

Name    Stmts   Miss  Cover   Missing
-------------------------------------
TOTAL   17837      0   100%

225 files skipped due to complete coverage.

[coveralls]

coverage: 99.985%. remained the same
when pulling e587a7f on keraion:RF03_tsql_merge
into d4ec93f on sqlfluff:main.

[alanmcruickshank]

Looks good!

btw @keraion - you've been tackling some really deep parts of the codebase over the last few months. Would you be interested in getting involved as a maintainer? Your github profile is fairly minimal so I can't see any contact details on there, but if you're interested - join the SQLFluff slack channel and drop me a DM. Would be great to have you as part of the team 😁 .