feat: Add getCommunicationInfo method and new prop to SafeInfo

[yagopv]

What it solves

Resolves safe-global/safe-apps-sdk#301, resolves safe-global/safe-react-apps#374

How this PR fixes it

We are doing 2 different things here:

1. Adding a new method getCommunicationInfo() used by returning some info about the communicator. By now we are returning the origin as we need it in the walletConnect app and is difficult to get it inside an iframe (Current approach ancestorOrigins is not supported on Firefox

2. We are including a new property isReadOnly on the SafeInfo object allowing as to know safe apps if the safe-web is on READ-ONLY mode

⚠️ Build going to fail until I update the pending SDK version with the methods and types ⚠️

[github-actions]

CLA Assistant Lite All Contributors have signed the CLA.

[github-actions]

ESLint Summary View Full Report

Annotations are provided inline on the Files Changed tab. You can also see all annotations that were generated on the annotations page.

Type	Occurrences	Fixable
Errors	0	0
Warnings	0	0
Ignored	0	N/A

• Result: ✅ success
• Annotations: 0 total

---

^{Report generated by eslint-plus-action}

[coveralls]

Pull Request Test Coverage Report for Build 1981898496

• 0 of 2 (0.0%) changed or added relevant lines in 1 file are covered.
• 29 unchanged lines in 4 files lost coverage.
• Overall coverage decreased (-0.02%) to 34.849%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
src/routes/safe/components/Apps/components/AppFrame.tsx	0	2	0.0%

Files with Coverage Reduction	New Missed Lines	%
src/routes/safe/components/Apps/components/AppFrame.tsx	2	0%
src/components/AppLayout/Header/components/ProviderDetails/PairingDetails.tsx	3	0%
src/components/AppLayout/Header/components/ProviderDetails/ConnectDetails.tsx	4	0%
src/components/AppLayout/Header/index.tsx	20	0%

Totals
Change from base Build 1969206373:	-0.02%
Covered Lines:	3375
Relevant Lines:	8776

---

💛 - Coveralls

[iamacook]

👍

[katspaugh]

Non-owners can still execute txns, so it's not 100% read-only.
Maybe isOwnedByMe: granted would be more descriptive?

[yagopv]

mmm could be, naming came from a conversation with Dani. WDYT @dasanra?

[mmv08]

Apps rather propose transactions than execute them, the nonowner cannot propose a transaction

[yagopv]

So what's the better option ? For me if nonowners cannot propose transactions isReadOnly could be fine as well in the safe-apps context

[iamacook]

This matches the Safe. We always show the read only warning if a user is not 'granted'.

[dasanra]

Yes, this isReadOnly is inspired as the Safe in the interface is shown as "Read Only" mode. The other name that could fit would be isOwnerConnected as we are trying to allow the apps to know if the owner is connected, so they can distinguish if that transaction could only be simulated or sent to be executed, either at that moment or later

[mmv08]

if the interface ever starts supporting delegates, isOwnerConnected may become non-relevant

[dasanra]

So, yes in this case the most relevant is to know if transaction could be sent or not, so isReadOnly should be good

[github-actions]

Deployment links

🟠 Rinkeby	⚪ Mainnet	🟣 Polygon	🟡 BSC	⚫ Arbitrum	🟢 Gnosis Chain