Update eslint rules

[compojoom]

What it solves

Reduces nitpicking on syntax during reviews.

Ads rules for enforcing shortharnd object notation and removing curly brace when having a single prop e.g.
something={"somtihng"} becomes sometihng="something"

I also tried adding jsx-newline, but it conflicts with prettier and there doesn't seem to be a setting that can make those 2 co-exist. So I gues nitpicking on non-readable jsx syntax is fine there :).

[github-actions]

Branch preview

✅ Deploy successful!

https://update_eslint_rules--walletweb.review-wallet-web.5afe.dev/home?safe=eth:0xA77DE01e157f9f57C7c4A326eeE9C4874D0598b6

[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}

[github-actions]

📦 Next.js Bundle Analysis for safe-wallet-web

This analysis was generated by the Next.js Bundle Analysis action. 🤖

One Page Changed Size

The following page changed size from the code in this PR compared to its base branch:

Page	Size (compressed)	First Load
/apps/open	66.8 KB (🟡 +1 B)	1.04 MB

Details

Only the gzipped size is provided here based on an expert tip.

First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

Next to the size is how much the size has increased or decreased compared with the base branch of this PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this.

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟡	Statements	79.38%	11081/13960
🔴	Branches	58.45%	2614/4472
🟡	Functions	65.94%	1785/2707
🟢	Lines	80.69%	9981/12370

Test suite run success

1404 tests passing in 194 suites.

Report generated by 🧪jest coverage report action from e32c567

[katspaugh]

LGTM! I've fixed the failing test on another branch.