[FEATURE REQUEST]: split up devicon.json

### I have searched through the issues and didn't find my problem.

- [X] Confirm

### Description

I had this idea before, and was reminded by the `check-bot` comment in https://github.com/devicons/devicon/pull/2135
I am not sure if this works for the whole build and release process, so i guess this needs more input.

**The Idea:**
Split up the `devicon.json` into snippets for each icon. So instead of having one huge json, split it up into a "one json per icon"
So in the example case of the `teleport` icon, we would have a folder like the following:


So each icon folder also includes a `devicon.json` or `teleport.json` (whatever fits better), including only the part specific for this icon.

When ever the full `devicon.json` is needed for build or publish it could be merged with a tool like `jq` or similar,
by iterating over all icon folders, and therefore automatically produce the alphabetical order we want.

### Context

I think the pro side of this split up is, that the contributors, don't need to have to remember that the alphabetical order is needed.

### Possible Solution

_No response_

### Additional information

_No response_

Esamina devicon.json e il commento di check-bot su PR #2135, quindi verifica come il processo di build e release utilizza il file. Determina se i file JSON delle singole icone possono essere uniti con jq o uno strumento simile preservando l’ordine alfabetico richiesto; il lavoro è completato quando l’approccio è stato convalidato per l’uso nel build e nella pubblicazione.

Scritto dal modello di indicizzazione a partire dal testo della issue.