fix(ui): layers explorer margin issue

[axel7083]

What does this PR do?

Avoid using runtime classes of tailwindcss, since tailwindcss do not generate classes if do not exists at compile time¹

Screenshot / video of UI

Before	After

What issues does this PR fix or reference?

Fixes #9410

How to test this PR?

• Tests are covering the bug fix or the new feature

Footnotes

1. https://stackoverflow.com/questions/69687530/dynamically-build-classnames-in-tailwindcss ↩

[feloy]

thanks for the fix

[benoitf]

wondering why we're kind using a flat display to represent a tree

Like why not using ul/li or parent/child ?

I mean, why there is a always a bigger shift from the left
I would expect that we only add a child that has always the same shift but as we're imbricating children, it does the tree /shift

[feloy]

wondering why we're kind using a flat display to represent a tree

Like why not using ul/li or parent/child ?

I mean, why there is a always a bigger shift from the left I would expect that we only add a child that has always the same shift but as we're imbricating children, it does the tree /shift

I remember trying this solution, but also encountering some other problem (sorry, cannot remember which one)

[axel7083]

Like why not using ul/li or parent/child ?

my proposal is to merge this as it fixes easily the issue, and we can open a technical issue on this one, is that okay with you @benoitf ?

[benoitf]

sure I'm not requesting changes