docs: update application references and improve clarity in documentation

- Replaced hardcoded application addresses with dynamic placeholders in the Oracle and iApp guides for better maintainability.
- Updated authorization app references to use dynamic variables in Web3Mail and Web3Telegram documentation.
- Enhanced clarity in the sendEmail and sendTelegram methods by improving the description of authorization requirements.

Author: Le-Caignec

src/get-started/protocol/oracle.md

@@ -131,7 +131,7 @@ dApp, and the parameters if applicable. The Oracle result writes in the
 
 ```bash
 $ cat ${IEXEC_OUT}/computed.json
-{ 'callback-data': '0x48656c6c6f2c20776f726c6421'}
+{ 'callback-data': '0x456def...'}
 ```
 
 When the computation ends the worker will send both this `callback-data`

src/guides/build-iapp/advanced/create-your-first-tdx-app.md

@@ -218,7 +218,7 @@ declaration
 await dataProtector.core.processProtectedData({
   protectedData: protectedData.address,
   workerpool: 'tdx-labs.pools.iexec.eth',
-  app: '0x1919ceb0c6e60f3B497936308B58F9a6aDf071eC',
+  app: '0x456def...',
 });
 ```
 

src/references/web3mail/methods/sendEmail.md

@@ -15,7 +15,7 @@ email must explicitly authorize you to send them email communications and
 permission must be granted for the `Web3Mail` tool to use the `protectedData`
 entity containing their email address. This is best done by granting
 authorization to the Web3Mail app whitelist
-`0x781482C39CcE25546583EaC4957Fb7Bf04C277D2` as `authorizedApp`. Refer to the
+`{{web3MailAppWhitelist}}` as `authorizedApp`. Refer to the
 [Data Protector `grantAccess`](/references/dataProtector/dataProtectorCore/grantAccess)
 documentation for more details.
 
@@ -399,4 +399,5 @@ const selectedChain = computed(() => userStore.getCurrentChainId());
 const chainData = computed(() => getChainById(selectedChain.value));
 const explorerUrl = computed(() => chainData.value.iexecExplorerUrl);
 const workerpoolAddress = computed(() => chainData.value.workerpoolAddress);
+const web3MailAppWhitelist = computed(() => chainData.value.web3MailAppWhitelist);
 </script>

src/references/web3telegram/methods/fetchUserContacts.md

@@ -21,7 +21,7 @@ const web3Provider = getWeb3Provider('PRIVATE_KEY');
 const web3telegram = new IExecWeb3telegram(web3Provider);
 // ---cut---
 const contactsList = await web3telegram.fetchUserContacts({
-  userAddress: '0xF048eF3d7E3B33A465E0599E641BB29421f7Df92',
+  userAddress: '0x789cba...',
 });
 ```
 
@@ -44,7 +44,7 @@ const web3Provider = getWeb3Provider('PRIVATE_KEY');
 const web3telegram = new IExecWeb3telegram(web3Provider);
 // ---cut---
 const contactsList = await web3telegram.fetchUserContacts({
-  userAddress: '0xF048eF3d7E3B33A465E0599E641BB29421f7Df92', // [!code focus]
+  userAddress: '0x789cba...', // [!code focus]
 });
 ```
 

src/references/web3telegram/methods/sendTelegram.md

@@ -15,7 +15,7 @@ message must explicitly authorize you to send them telegram communications and
 permission must be granted for the `Web3Telegram` tool to use the
 `protectedData` entity containing their chat ID. This is best done by granting
 authorization to the Web3Telegram app whitelist
-`0x192C6f5AccE52c81Fcc2670f10611a3665AAA98F` as `authorizedApp`. Refer to the
+`{{web3TelegramAppWhitelist}}` as `authorizedApp`. Refer to the
 [Data Protector `grantAccess`](/references/dataProtector/dataProtectorCore/grantAccess)
 documentation for more details.
 
@@ -298,4 +298,5 @@ const selectedChain = computed(() => userStore.getCurrentChainId());
 const chainData = computed(() => getChainById(selectedChain.value));
 const explorerUrl = computed(() => chainData.value.iexecExplorerUrl);
 const workerpoolAddress = computed(() => chainData.value.workerpoolAddress);
+const web3TelegramAppWhitelist = computed(() => chainData.value.web3TelegramAppWhitelist);
 </script>