Update Pearl trader

[jmoreira-valory]

Update Pearl trader for the refactored branch on olas-operate.

⚠️ Important: This update is for the current trader_pearl used in olas-operate #344, which is referenced here: https://github.com/valory-xyz/olas-operate-app/blob/da917f717745a09f4548d0d239f4e4e6e8394748/frontend/constants/serviceTemplates.ts#L7 and introduces the changes required for the refactored branch valory-xyz/olas-operate-app#428, which mainly concerns the introduction of environment variables.

[OjusWiZard]

diff from bafybeidicxsruh3r4a2xarawzan6ocwyvpn3ofv42po5kxf7x6ck7kn22u to this trader_pear/service.yaml is this: https://www.diffchecker.com/HY2yJFMe/

[jmoreira-valory]

@Adamantios confirm that the trader_pearl configuration in this PR is appropriate for 0.18.2 / 0.18.7

[Adamantios]

@Adamantios confirm that the trader_pearl configuration in this PR is appropriate for 0.18.2 / 0.18.7

The configs look good from a framework's perspective. Could you elaborate on that more?

[jmoreira-valory]

The comment is about if you could check if the pearl_trader.yaml is missing (or has an inconvenient value) for any config params that have been introduced recently, in terms of of tools/multibets/simulation/... etc.

[Adamantios]

The comment is about if you could check if the pearl_trader.yaml is missing (or has an inconvenient value) for any config params that have been introduced recently, in terms of of tools/multibets/simulation/... etc.

You could diff with the main service config and use the exact same defaults. I think we could merge the two service files anyway.