Add styling json file

[kaamyashinde]

These JSON files will be used in the styling system that will be setup

Issue
Resolves #14048

Approach
Added the two json files that were sent by the EDS team. Parent folder was also renamed to styling and sub folders were introduced based on the role of the files

• PR title captures the intent of the changes, and is fitting for release notes.
• Added appropriate release note label
• Commit history is consistent and clean, in line with the contribution guidelines.
• Make sure unit tests pass locally after every commit (git rebase -i main --exec 'just rapid-tests')

When applicable

• When screenshots are changed: Review screenshot-PR in ert-testdata,
  merge screenshot-PR in ert-testdata before merging this PR.
• When there are user facing changes: Updated documentation
• New behavior or changes to existing untested code: Ensured that unit tests are added (See Ground Rules).
• Large PR: Prepare changes in small commits for more convenient review
• Bug fix: Add regression test for the bug
• Bug fix: Add backport label to latest release (format: 'backport release-branch-name')

[SAKavli]

Looking good!
I am not convinced by my own opinion, but what do you think of the structure:
/styles/themes/{dark,light}.json ?
Are dark/light considered styles or themes?
And in the future we will add style objects, how do these fit into the folder structure?
Would also love @eilskra 's opinion!

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.81%. Comparing base (d9fe003) to head (0fc52e1).
⚠️ Report is 6 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #14058      +/-   ##
==========================================
- Coverage   91.84%   91.81%   -0.04%     
==========================================
  Files         480      480              
  Lines       33337    33402      +65     
==========================================
+ Hits        30619    30667      +48     
- Misses       2718     2735      +17     

Flag	Coverage Δ
cli-tests	36.24% <0.00%> (-0.11%)	⬇️
fuzz	44.08% <100.00%> (-0.04%)	⬇️
gui-tests	58.33% <0.00%> (-0.06%)	⬇️
performance-and-unit-tests	80.42% <100.00%> (+0.03%)	⬆️
test	46.41% <0.00%> (-0.05%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
src/ert/gui/styling/__init__.py	100.00% <100.00%> (ø)
src/ert/gui/styling/theme_manager/manager.py	100.00% <ø> (ø)
src/ert/gui/styling/theme_manager/theme.py	100.00% <ø> (ø)

... and 10 files with indirect coverage changes

[kaamyashinde]

we currently have the manager.py which is the theme manager that is responsible for translating the json for qt to be able to processed. So perhaps the whole folder should be restructured in some way.

perhaps something like the following, where the future .qss.in file that applies the styling can be added inside the qss_styling folder, in case we want to have one file per component. So f.eks

Additionally, we can drop the qss_styling folder as of now and just place the .qss.in file inside the styling folder.

@SAKavli @eilskra

[eilskra]

I vote either themes or maybe color_schemes?
e.g /styles/themes/{dark,light}.json

Components could maybe just go under maybe style_sheets or something, maybe something along the lines of:

styles/
-- color_schemes/
---- {dark,light}.json
-- style_sheets/
---- qss.in 

[eilskra]

perhaps something like the following, where the future .qss.in file that applies the styling can be added inside the qss_styling folder, in case we want to have one file per component. So f.eks

Or like that, I vote this 👍

[codspeed-hq]

Merging this PR will not alter performance

✅ 36 untouched benchmarks

---

_{Comparing add-styling-json-file (0fc52e1) with main (793ddcd)}

[eilskra]

Nice! 🥇