feat(topic-rules): Add copy and paste functionality

[Strazz1337]

Pull Request description

#301

Adds the ability to copy topic rules and paste topic rules. This change also extracts the chiplist logic to a separate component because it is now duplicated thrice.

Before

After

Screen.Recording.2026-04-02.at.12.38.03.mov

General checklist

• You have reviewed the guidelines document.

I did not see another suitable branch other than main, due to the other branches being outdated.

• Labels that classify your pull request have been added.
• The milestone is specified and corresponds to fix version.
• Description references specific issue.
• Description contains human-readable scope of changes.
• Description contains brief notes about what needs to be added to the documentation.
• No merge conflicts, commented blocks of code, code formatting issues.
• Changes are backward compatible or upgrade script is provided.

Front-End feature checklist

• Screenshots with affected component(s) are added. The best option is to provide 2 screens: before and after changes;
• If you change the widget or other API, ensure it is backward-compatible or upgrade script is present.

Back-End feature checklist

• Added corresponding unit and/or integration test(s). Provide written explanation in the PR description if you have failed to add tests.
• If new dependency was added: the dependency tree is checked for conflicts.

[deaflynx]

Thanks for the contribution! Nice refactoring of the duplicated chip-list logic.

One concern: Adding COMMA as a separator key will break regex quantifier patterns like sensor/.{1,3} — the comma would split it into two invalid chips (sensor/.{1 and 3}). MQTT auth rules support regex, so this is a realistic user input. Consider removing COMMA from the separator keys. SEMICOLON is fine to keep — it has no special meaning in regex and is not used in MQTT topics.