[Address book v2] Address book update events

[dasanra]

What:
Closes #2240 #2252
This PR is intended to do a check on the address book add, update and remove events. It will ensure that in each place where a name can be added or edited its value is stored in the address book

Why:
We want to ensure that we use a central source of truth, and so we are relaying on the address book to create the relationship between an address and a name, instead of keeping update in two places for the case of safe owners and an added safe

How:
I did a review of all places where an address name can be edited and ensured that this changes were persisted in the address book. Then I also ensured that on every place that we show an address name this value is picked from the address book

How to test it:

• Create safe – safe name is stored in the address book
• Load safe - safe name is stored in the address book
• Add an owner - check name in address book
• Replace an owner - check name in address book
• Edit safe name in settings
• Edit owner name in settings
• Directly create an address book entry
• Directly edit an address book entry
• Check that address book name is shown on transaction details
• Name stored in address book it's used over known address name from client-gateway
• Deleting a safe using settings button don't delete the address from the address book
• Name shown in assets "send" is updated
• Name shown in assets "receive" is updated
• Name shown in transaction details for owners is correct
• Name shown in address book "send" is correct
• Names shown in settings > spending limits are correct

Checklist:

• Ready to be merged
  

[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	1	0
Ignored	0	N/A

• Result: ✅ success

• Annotations: 1 total

  ---

[warning] @typescript-eslint/explicit-module-boundary-types

Require explicit return and argument types on exported functions' and classes' public class methods

• src/routes/load/components/DetailsForm/index.tsx Line 49 - Argument 'values' should be typed.

---

^{Report generated by eslint-plus-action}

[github-actions]

• Safe Multisig app mainnet

[github-actions]

• Safe Multisig app rinkeby

[katspaugh]

Looks great! 🚀

[fernandomg]

🚀

[katspaugh]

I'll move the "how to test" section from this PR to the epic where it was merged.