New Linter: Generic conflictingmarkers

[yongruilin]

Description

Create a new, configurable linter named conflictingmarkers to detect and report when mutually exclusive markers are used on the same field. This prevents common configuration errors and unexpected behavior.

Problem

There is currently no generalized way to prevent the use of conflicting markers. For example, a field cannot have both a default value and be required. This linter will provide a flexible solution to this and similar issues.

Requirements

1. Generic Conflict Detection: The linter should identify fields that have markers from two conflicting sets.

2. Built-in Rules: It must include checks for the following initial conflicts:

   • optional vs. required:
     • Set A: optional, +kubebuilder:validation:Optional
     • Set B: required, +kubebuilder:validation:Required
   • default vs. required:
     • Set A: default, +kubebuilder:default
     • Set B: required, +kubebuilder:validation:Required

3. Configurability: Allow users to define their own custom sets of conflicting markers in the linter's configuration.

[yongruilin]

/assign
I have some time to implement this this or early next week.

[JoelSpeed]

@yongruilin Do you think we can close this one now that #126 is merged?

[yongruilin]

Do we want to keep it to track for child linters that use this base linter or we can close it and create separate ones.

[JoelSpeed]

I think lets create separate issues for the child linters