fix: Range-color-profile-name.js not using the correct profile name

[Trainermitch]

Range-color-profile-name.js was using a map iterator object as the profile name instead of the actual string name. Changed the input from a map to an array. Also added a check to make range profile names non case sensitive.

• I have thoroughly tested all of the code I have modified/added/removed to ensure something else did not break
• I have followed semantic commit messages e.g. feat: Add foo, chore: Update bar, etc...
• My branch has a clear history of changes that can be easy to follow when being reviewed commit-by-commit
• My branch is functionally complete; the only changes to be done will be those potentially requested in code review
• All changes requested in review have been fixuped into my original commits.
• Fully tokenized all my strings (no hardcoded English strings!!) and supplied bulk JSON strings below

[tsa96]

Hi, thanks for the PR!

CI is currently failing due to formatting issues, I suggest running npm install and npm run format:fix in the root directory (as detailed in the repo readme), then please amend/fixup that change into your original commit and force-push.

I'll review properly in next few hours!

[tsa96]

Yeah good catch, these fixes seem correct. I'm afraid Prettier wants to do some silly line breaking though, will need to run formatter to get CI to pass (I know, auto formatting stuff can be annoying to faff with, but well worth it for sake of clean code).

[Trainermitch]

I reformatted, did that work? This is my first time using github.

[tsa96]

Yup, all good! Congrats on your first PR!