[HOLD for payment 2024-06-20] Change icon of the hub connections.

[rushatgabhane]

Slack: https://expensify.slack.com/archives/C02QSAC6BJ8/p1717772156939879

Following these steps: https://github.com/Expensify/App/tree/main/docs#how-to-change-icon-of-a-hub

We have to change the illustration of connections hub for both platforms - Expensify Classic and New Expensify

[melvin-bot]

Triggered auto assignment to @dylanexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[dannymcclain]

Hey @dylanexpensify, this isn't really a bug, just a quick design update, so I unassigned you and assigned myself.

@rushatgabhane thanks for the guidance!

[dannymcclain]

cc @maddylewis just so you have eyes on this. I should be able to get to it Monday.

[dannymcclain]

PR open ☝️

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.82-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• New connections illustration and apply it to both accounting integration hubs #43401

If no regressions arise, payment will be issued on 2024-06-20. 🎊

[melvin-bot]

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

• [] The PR that introduced the bug has been identified. Link to the PR:
• [] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
• [] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
• [] Determine if we should create a regression test for this bug.
• [] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
• [] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

[rushatgabhane]

checklist / payment not applicable