feat: Add search functionality to macro settings interface

[mnigbur]

Description

This PR adds search functionality to the macro settings interface

Related Tickets & Documents

none

Mobile & Desktop Screenshots/Recordings

[optional] Are there any post-deployment tasks we need to perform?

none

[github-actions]

Language file analysis report:

File	Missing Keys	Unused Keys
cz.json	349	23
da.json	54	12
de.json	1	0
en.json	0	0
es.json	24	21
fr.json	202	15
hu.json	25	24
it.json	22	3
ja.json	350	22
ko.json	346	22
nl.json	280	22
pl.json	230	13
pt.json	323	21
ru.json	0	0
se.json	200	14
tr.json	277	19
uk.json	61	5
zh.json	1	1
zh_TW.json	342	21

[github-actions]

Language file analysis report:

File	Missing Keys	Unused Keys
cz.json	348	22
da.json	54	12
de.json	1	0
en.json	0	0
es.json	24	21
fr.json	202	15
hu.json	25	24
it.json	22	3
ja.json	350	22
ko.json	346	22
nl.json	280	22
pl.json	230	13
pt.json	323	21
ru.json	0	0
se.json	200	14
tr.json	277	19
uk.json	61	5
zh.json	1	1
zh_TW.json	342	21

[meteyou]

@mnigbur thx for this PR!

are you a native speaker in all these languages? normally we only add english and our native language (in my case germany). all other languages should be added by the translators.

Could you also change the layout of the search field? for example like this in the gcode file panel:

so it should not be the same "style/layout" as the normal "input fields for settings".

[github-actions]

Language file analysis report:

File	Missing Keys	Unused Keys
cz.json	348	22
da.json	54	12
de.json	1	0
en.json	0	0
es.json	24	21
fr.json	202	15
hu.json	25	24
it.json	22	3
ja.json	350	22
ko.json	346	22
nl.json	280	22
pl.json	230	13
pt.json	323	21
ru.json	0	0
se.json	200	14
tr.json	277	19
uk.json	61	5
zh.json	1	1
zh_TW.json	342	21

[mnigbur]

@mnigbur thx for this PR!

are you a native speaker in all these languages? normally we only add english and our native language (in my case germany). all other languages should be added by the translators.

Could you also change the layout of the search field? for example like this in the gcode file panel:

so it should not be the same "style/layout" as the normal "input fields for settings".

@meteyou
The translation for "search" already existed for all languages, so i prefilled it for all of them.
What's the issue with prettier? I did run the script before committing. CLRF issue?