Sync palindrome products exercise with problem specification

[themetar]

[As discussed on the forum]

• Added the missing test cases
• Updated the example solution to comply to new tests

[github-actions]

Hello. Thanks for opening a PR on Exercism 🙂

We ask that all changes to Exercism are discussed on our Community Forum before being opened on GitHub. To enforce this, we automatically close all PRs that are submitted. That doesn't mean your PR is rejected but that we want the initial discussion about it to happen on our forum where a wide range of key contributors across the Exercism ecosystem can weigh in.

You can use this link to copy this into a new topic on the forum. If we decide the PR is appropriate, we'll reopen it and continue with it, so please don't delete your local branch.

If you're interested in learning more about this auto-responder, please read this blog post.

---

Note: If this PR has been pre-approved, please link back to this PR on the forum thread and a maintainer or staff member will reopen it.

[github-actions]

This PR touches files which potentially affect the outcome of the tests of an exercise. This will cause all students' solutions to affected exercises to be re-tested.

If this PR does not affect the result of the test (or, for example, adds an edge case that is not worth rerunning all tests for), please add the following to the merge-commit message which will stops student's tests from re-running. Please copy-paste to avoid typos.

[no important files changed]

For more information, refer to the documentation. If you are unsure whether to add the message or not, please ping @exercism/maintainers-admin in a comment. Thank you!

[kotp]

You should be able to apply the suggestions, they are simply to provide a blank line after visibility methods private and public as they do not affect only the following line.

[kotp]

Suggested change

	private
	attr_reader :min, :max
	private
	attr_reader :min, :max

[themetar]

vscode kept triggering rubocop and auto-formatting my code. I assumed that that's exercism's style.

I think this is the rule that's being followed:

ruby/.rubocop.yml

Lines 37 to 38 in fa35ccc

	Layout/EmptyLinesAroundAccessModifier:
	EnforcedStyle: only_before

[kotp]

It is stating that it is only enforcing the empty line before. But, while we are not enforcing that there is a blank line after (because sometimes that really does make sense) we may have a blank line, and so should likely have a blank line after, since the communication value is there.

[kotp]

Suggested change

	public
	attr_reader :smallest, :largest
	public
	attr_reader :smallest, :largest

[themetar]

I've added the blank lines. @kotp

[kotp]

It is stating that it is only enforcing the empty line before. But, while we are not enforcing that there is a blank line after (because sometimes that really does make sense) we may have a blank line, and so should likely have a blank line after, since the communication value is there.