Implement automated validation for the RHDH Release Notes Process in the jira-lint tool. This will enforce Release Note field requirements for Features and Bugs based on release-phase dates and send notifications to relevant stakeholders.

Jira is the single source of truth for Release Notes. The Release Note Type field is now required on Features and Bugs. The jira-lint tool needs to validate these fields and notify team members of violations based on release phase deadlines (Feature Freeze, Code Freeze).

RHDH RNs Process: https://docs.google.com/document/d/1KFMkRVTkbDIhyZviZcuVn9UfJp64lKmokzT4ftMrj4w/edit?tab=t.0#heading=h.afxqdu5skyve

Acceptance Criteria

1. Release Note Type Validation (Feature Freeze)

• Trigger violation for Features in RHIDP+RHDHPLAN project when Release Note Type is not set after Feature Freeze date
• Violation message should guide users to set appropriate Release Note Type

2. Release Note Text Validation (Code Freeze)

• Trigger violation for Features in RHIDP+RHDHPLAN when `Release Note Text` is Empty AND `Release Note Type` != "Release Note Not Required" after Code Freeze date
• Exemption: Skip validation if `Release Note Type` == "Release Note Not Required"

3. Documentation Team Notifications

• Send Slack notification to @rhdh-docs user group when:
    - `Release Note Text` is NOT Empty AND
    - `Release Note Type` is NOT Empty AND
    - `Release Note Status` != "Done"
• Notification should include issue key, summary, and link to review
• Group multiple issues in a single notification to @rhdh-docs (don't spam)

5. Testing & Validation

• Test with DRY_RUN mode against test Jira issues