ci: fix frontend workflow and remove duplicate PR title checks

[Pcmhacker-piro]

Closes #1092

PR Description

This PR fixes repository CI workflow configuration issues by updating the frontend CI workflow and the knip check workflow. It also removes the duplicate PR title checker workflow and its related configuration file to avoid redundant validation.

Type of Change

• Bug fix (change which fixes an issue)
• New feature (change which adds functionality)
• Documentation update

Select your work-area

• Frontend
• Backend
• Documentation
• Others

Related Issue

Resolves issue #1092

Add your Work Example

📷 Add a Snapshot

Not applicable for this change, since this PR only updates GitHub workflow/configuration files.

Fixes (mention the issue number which this fixes)

#1092

Checklist

• I have updated my branch and synced it with the project's 'develop' branch before making this PR.
• I have optimized the file changes.
• I have added a snapshot of my work example.
• I have made a PR to the project's develop branch.

Undertaking

• My code follows the style guidelines of this project.

• I have performed a self-review of my code.

• I have commented my code, particularly in hard-to-understand areas.

• I have made corresponding changes to the documentation.

• I have checked for plagiarism and assure its authenticity.

• I have read and followed the code of conduct for this repository. I understand that violation of this undertaking may have legal consequences.

• I Agree

[github-actions]

Thank you @, for creating the PR and contributing to our UltimateHealth project 💗.
Our team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

[Pcmhacker-piro]

heyy @SB2318
i fixed the assign issue so pls check it

[SB2318]

@Pcmhacker-piro Please create an issue first, describe your proposed changes.

[Pcmhacker-piro]

heyy @SB2318
this is the my issue link #1092

[Pcmhacker-piro]

heyy @SB2318
i fixed the assign issue so pls check it

[Pcmhacker-piro]

heyy @SB2318
i fixed the issue so pls check this

[gitguardian]

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
While these secrets were previously flagged, we no longer have a reference to the
specific commits where they were detected. Once a secret has been leaked into a git
repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.

---

^{_{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}}

[Zganz404]

Approach is solid. Minor nit: this would benefit from a brief comment explaining why we skip validation for internal callers.

[Pcmhacker-piro]

Hi! I have investigated the failing CI checks for this PR.

After fixing the issues directly related to this PR, I found that the main branch itself has pre-existing typecheck and linting failures (38 errors across 6 files), which is preventing this PR from passing its required status checks.

I have opened a separate issue for the maintainers to stabilize the main branch: #1227.

Please stabilize main so that this PR can be properly validated and merged.