feat: add configurable acceptable warning threshold

[k1LoW]

This pull request refactors how lint configuration is structured and introduces a new feature to control the acceptable number of lint warnings before failing. The main changes are the introduction of an acceptable threshold for warnings, the grouping of all lint rules under a new rules field, and updates to both the code and documentation to reflect these changes.

Configuration structure improvements:

• Added an acceptable field to the lint configuration, allowing users to specify the maximum number of lint warnings before the command fails. This is documented in the README.md and implemented in the lint command logic. [1] [2] [3] [4]
• Refactored the configuration so that all lint rules are now grouped under a new rules field within the lint section, replacing the previous flat structure. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11]

Code and test updates:

• Updated all usages of lint rule configuration in the codebase to reference the new rules field, ensuring consistency and correctness. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]
• Updated all related tests to use the new rules field, ensuring tests reflect the new configuration structure and continue to validate linting logic. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15]

Documentation:

• Updated the README.md to document the new acceptable option and the new structure for specifying lint rules. [1] [2]

Other:

• Minor code cleanup: removed an unused import from cmd/lint.go.

[github-actions]

Code Metrics Report

Coverage	Code to Test Ratio
33.0%	1:1.5

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

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

---

Reported by octocov