Fix: signer vs plural signers

[katspaugh]

What it solves

Resolves a comment by Franco:

minor issue

There is a ticket where we changed signer/signers depending on if there was more than 1 signer.
There is the situation where if a user is removed from a safe with 2 owners, the ending result should say "1 out of 1 signer" but it still says signers:
- Have a safe with 2 owners
- Remove one
- In the review step, just before executing, see the wording

[github-actions]

Branch preview

✅ Deploy successful!

Website:
https://signers--walletweb.review.5afe.dev/home?safe=eth:0xA77DE01e157f9f57C7c4A326eeE9C4874D0598b6

Storybook:
https://signers--walletweb.review.5afe.dev/storybook/

[github-actions]

Code review by ChatGPT

[github-actions]

Consider moving maybePlural logic out of template literal for clarity. Refactor to use a single function call within the component to determine singular or plural form, to enhance readability and maintainability.

[github-actions]

1. Consider renaming maybePlural to something more descriptive like pluralizeIfNeeded to enhance readability.
2. Inline logic for pluralization could be moved to a utility file if used across multiple components, adhering to DRY principles.

[github-actions]

Ensure the conditional for singular/plural form is accurate. Changing "signers" to "signer" might be incorrect if it's intended for a plural context. Verify the logic, handling both singular and plural cases to avoid linguistic errors.

[github-actions]

 const newSignersLength = safe.owners.length + ('removedOwner' in settingsInfo ? 0 : 1);

Consider encapsulating the logic to determine the number of signers inside a function for clarity and reuse. This will simplify the component and improve code readability.

[github-actions]

Ensure that the change from "signers" to "signer" does not impact any logic that depends on the plurality of signers. Verify surrounding code for logic that might assume a list or count of signers, and adjust business logic if applicable.

[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
/settings/setup	30.81 KB (🟡 +12 B)	1.02 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	73.84% (+0% 🔼)	14385/19480
🔴	Branches	51.39%	3433/6680
🔴	Functions	56.77%	2041/3595
🟡	Lines	75.37% (+0% 🔼)	13045/17308

Test suite run success

1707 tests passing in 231 suites.

Report generated by 🧪jest coverage report action from e4a5f7a