[Code Quality + Security] capture-app-ionic. Unify iframe postMessage format and extract to ENUMs

[sync-by-unito]

Based on ChatGPT suggestion
some places use kebab-case some places use camleCase.
For capture-app-ionic

• find all postMessage.data and make sure all are kebab-case
• find all postMessage.data and use ENUMs instead of plain string

┆Issue is synchronized with this Asana task by Unito
┆Created By: Sam

[sync-by-unito]

➤ Kenny Hung commented:

Sam (cc Tammy YangEthan Wu)
Does this task affect iframe back button, right? There are some questions need to confirm.

1. I found iframe back button on "terms of use" page can't work, it needs iframe-v230209 deployed and it could work. Does it correct?
2. So, in order to avoid the above issue, iframe-v230209 should wait for ionic-v230209 public, the conclusion correct?

[sync-by-unito]

➤ Sam commented:

Kenny Hung, yes correct.
When we were first experimenting with postMessages I made a mistake and used "iframeBackButtonClicked" as a command. But now we changed it to iframe-back-button-clicked to make sure all events are kebab-case not camleCase.

[sync-by-unito]

➤ Kenny Hung commented:

Sam Got it. Thanks for explanation.
Another curious question, why FAQ and iframe wallet page doesn't affect by this change? They are also iframe page.

[sync-by-unito]

➤ Sam commented:

Kenny Hung,
Yes FAQ and Wallets page are 100% iframe.

regarding FAQ page:

• I built FAQ page and used iframe-back-button-clicked as trigger so it should work

regarding Wallet page

• I checked the code and it uses iframeBackButtonClicked as trigger and it should not work 🤔.