fix(window): use stored size for new floating window when persistentsize is set

[yuukibarns]

Describe your PR, what does it fix/add?

fix #9422.

When open a floating window (i.e. windowrule float applied on the window), it should use the stored size if persistentsize is set.

Is it ready for merging, or does it need work?

I want to further improve the windowrule persistentsize by storing the sizes in cache or config file so that sizes can be persistent across boots, but I am a newbie in C++ and I don't know the conventional method to do this in this project, so I will wait for your kind instructions.

[yuukibarns]

Related #10161

[yuukibarns]

COMMIT 1: use stored size for new floating window
COMMIT 2: replace any_of with ranges::any_of
COMMIT 3: use initialClass and initialTitle when storing sizes on close

May I explain the COMMIT 3. The previous implementation use class and title when storing sizes on close but I find title can be too changeable to be used as an indicator (for example title of anki's Browse page is like Browse (Selected xxx from xxx)), so I think it can be more reliable to use initialClass and initialTitle.

However, this introduce a new problem, see below.

[yuukibarns]

However, there are still problems to solve:

1. some windows can have the same initialTittle and initialClass, (for example, anki's browse and syncing);
2. store size information in caches or config files for persistence across boots.

[vaxerski]

2 is too complicated to do in this MR, I say leave it.
1 you can incorporate the xdg-tag protocol here for when these apps start supporting it

[vaxerski]

rest lgtm

[yuukibarns]

However, there are still problems to solve:

1. some windows can have the same initialTittle and initialClass, (for example, anki's browse and syncing);

2. store size information in caches or config files for persistence across boots.

Any plan on 2?

[vaxerski]

not for now