remove duplicates of languages from tooling-data.yml

[Vishv0407]

What kind of change does this PR introduce?
Bug fix - remove two caseInsensetive entries of same name such as 'JavaScript' and 'Javascript'

Issue Number:

• Closes 🐛 Bug: Two JavaScript labels for filter on Tools page #1443
• Related to #___
• Others?

Screenshots/videos:

If relevant, did you update the documentation?
No.

Summary
Mainly I update languages which contains duplicate entries.

Does this PR introduce a breaking change?
No

[github-actions]

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name	Status	Preview	Last Commit
website	✅ Ready (View Log)	Visit Preview	7cedaf6

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (219521e) to head (7cedaf6).

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #1512   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           10        10           
  Lines          396       396           
  Branches       106       106           
=========================================
  Hits           396       396           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Vishv0407]

@benjagm I recently opened a PR(I closed) but it failed a check for changing unauthorized file. here is the proposal before making changes in those files.

Feature - Adds case-insensitive unique validation for language entries

Screenshots/videos:
Forcefully made mistakes in the name of language,

Validator finds the mistake,

Summary
This PR introduces case-insensitive unique validation for language entries in the tooling data to solve several existing problems:

1. Inconsistent language casing across tools (e.g., "JavaScript" vs "javascript" vs "JAVASCRIPT")
2. Potential confusion for users seeing the same language listed multiple times

My solution:
Implements a custom AJV keyword caseInsensitiveUnique that:

• Detects and reports case-insensitive duplicates using set
• Provides clear error messages for easy fixes

           ajv.addKeyword({
              keyword: 'caseInsensitiveUnique',
              type: 'array',
              validate: function (schema, data) {
                if (!Array.isArray(data)) return false;
                
                const languagesSet = new Set();
                const languagesLowercaseSet = new Set();
                data.forEach((tool) => {
                  if (tool.languages) {
                    tool.languages.forEach((language) => {
                      languagesSet.add(language);
                      languagesLowercaseSet.add(language.toLowerCase());
                    });
                  }
                });
                if (languagesSet.size !== languagesLowercaseSet.size) {
                  console.error('Duplicate languages found');
                  const lowercaseMap = new Map();
                  languagesSet.forEach((language) => {
                    lowercaseMap.set(
                      language.toLowerCase(), 
                      (lowercaseMap.get(language.toLowerCase()) || 0) + 1
                    );
                  });
                  
                  lowercaseMap.forEach((value, key) => {
                    if (value > 1) {
                      console.log('Duplicate found for:', key);
                    }
                  });
                  validate.errors = [{
                    keyword: 'caseInsensitiveUnique',
                    message: 'array contains case-insensitive duplicates',
                    params: { keyword: 'caseInsensitiveUnique' }
                  }];
                  return false;
                }
                return true;
              }
            });

For Tool Maintainers:

# Before
languages:
  - "JavaScript"
  - "javascript"
  - "Python"
  - "PYTHON"

# After
languages:
  - "JavaScript"  # Use consistent casing from schema enum
  - "Python"

What's your feedback on this approach?

[DhairyaMajmudar]

Thanks for the PR @Vishv0407 but it seems these changes are already covered in your PR #1513

Closing this in response of it.