feature: Add shouldRetry option

[pukuba]

Referencing #67 and #70, I've added the shouldRetry option.

Please review when you have time.

Fixes #70

[pukuba]

I've checked the comments on the issue. Here are my thoughts.

In pRetry, using the shouldRetry method is beneficial for reducing the complexity of retry logic, enhancing code readability, and promoting reusability.

• Reducing Complexity: The shouldRetry method allows for detailed error handling, enabling specific conditions for retrying. This separation of concerns simplifies the overall structure of the code.
• Enhancing Code Readability: With shouldRetry, the retry logic is clear and concise, making the code easier to read and understand. It allows developers to easily discern under what conditions a retry will be attempted.
• Promoting Reusability: The shouldRetry method can be reused across different parts of the application, ensuring consistency and reducing the need for redundant code.

Certainly, using bail is a good method, but I also think adding a shouldRetry option to p-retry is a good approach.

Respecting the code owner's opinion. If you have any additional thoughts, please leave a comment! @sindresorhus

[sindresorhus]

Not sure I trust this pull request. Your comment is clearly ChatGPT, so I'm going to assume the code changes are too.

[pukuba]

I didn't use GPT to write code, but I used it to write PR because I'm not good at English.
The comment I wrote before contains my thoughts.

If you want to close, you can close. Feel free to give me your opinion.

[sindresorhus]

You need to add it to the readme too.

[sindresorhus]

Suggested change

	shouldRetry is not called for TypeErrors (except network errors) and AbortError.
	It is not called for `TypeError` (except network errors) and `AbortError`.

[sindresorhus]

index.d.ts too

[madmed88]

is it possible to backport this to v4?