fix(slides): resolve prototype pollution in swiper v5

[liamdebeasi]

Pull request checklist

Please check if your PR fulfills the following requirements:

• Tests for the changes have been added (for bug fixes / features)
• Docs have been reviewed and added / updated if needed (for bug fixes / features)
• Build (npm run build) was run locally and any changes were pushed
• Lint (npm run lint) has passed locally and any fixes were made for failures

Pull request type

Please check the type of change your PR introduces:

• Bugfix
• Feature
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation content changes
• Other (please describe):

What is the current behavior?

Issue Number: resolves #23342

What is the new behavior?

• Ejected from the swiper bundling process so that we can backport a swiper v6 fix to swiper v5
• This means we cannot easily upgrade to next swiper, but Framework v6 is bringing changes that makes this a non-issue.
• Copied fix from nolimits4web/swiper@ec358de#diff-900b2578438f0dfc98ec3ea732e1fed0aba5c31be5f21201c4311f0737c76fa0

Does this introduce a breaking change?

• Yes
• No

Other information

[3zzy]

but Framework v6 is bringing changes that makes this a non-issue

@liamdebeasi Ionic Framework v6 will get rid of SwiperJS you mean?

[liamdebeasi]

We are not getting rid of SwiperJS in Framework v6, but we are going to be recommending that developers use the framework integrations provided by the Swiper team instead. We will have more information as we get closer to the v6 launch.