fix: replace legacy permission support to deprecated

[k1LoW]

This pull request consolidates the handling of deprecated and legacy permission patterns in TailorDB linting, streamlining configuration and messaging. The main change is the removal of the separate legacyPermission lint rule and its integration into the existing deprecatedFeature rule, both in configuration and code. Documentation and tests are updated accordingly for clarity and consistency.

Configuration and Lint Rule Simplification:

• Removed the legacyPermission lint rule from the .patterner.yml configuration and merged its functionality into the deprecatedFeature rule for TailorDB, simplifying the config structure and reducing duplication. [1] [2]
• Updated the deprecatedFeature rule in documentation and code to cover detection of both deprecated features and legacy permission patterns, and clarified the description and relevant documentation links. [1] [2]

Code and Test Refactoring:

• Refactored code in tailor/lint.go to check for deprecated type and record permissions under DeprecatedFeature instead of the removed LegacyPermission, and updated warning messages to use "deprecated" terminology.
• Updated tests in tailor/lint_test.go and test configuration in tailor/helper_test.go to use the new structure and to expect "deprecated" instead of "legacy" in warning messages. [1] [2] [3] [4]

Documentation Update:

• Added missing workspaceID field to the example configuration in README.md for completeness.

[github-actions]

Code Metrics Report

Coverage	Code to Test Ratio
33.3%	1:1.5

Code coverage of files in pull request scope (73.8%)

Files	Coverage
config/config.go	0.0%
tailor/lint.go	98.4%

---

Reported by octocov