Update ip-ranges.adoc show deprecation of macOS IPs

[labsquared]

Description

Add note to indicate deprecation of known macOS IPs.

Reasons

macOS well-known IPs are no longer supported after April 24, 2024.

Content Checklist

Please follow our style when contributing to CircleCI docs. Our style guide is here: https://circleci.com/docs/style/style-guide-overview.

Please take a moment to check through the following items when submitting your PR (this is just a guide so will not be relevant for all PRs) 😸:

• Break up walls of text by adding paragraph breaks.
• Consider if the content could benefit from more structure, such as lists or tables, to make it easier to consume.
• Keep the title between 20 and 70 characters.
• Consider whether the content would benefit from more subsections (h2-h6 headings) to make it easier to consume.
• Check all headings h1-h6 are in sentence case (only first letter is capitalized).
• Is there a "Next steps" section at the end of the page giving the reader a clear path to what to read next?
• Include relevant backlinks to other CircleCI docs/pages.

[kelvintaywl]

i'm sorry to request changes here, but thinking on behalf of readers/customers, I wonder if we can announce this change better?
I hope you can hear me out 🙇

1. Leaving the listed IP ranges around can cause confusion; I'd argue removing the listed IP ranges would be less confusing.
2. this change would mean that the following text is still there, which can also confuse

macOS builds are automatically restricted within the IP ranges listed here. In other words, you do not have to explicitly set circleci_ip_ranges: true for macOS builds.
(ref)

If we prefer setting the on its deprecation, can we be verbose and say something like "the earlier list of IP ranges are no longer supported/guaranteed for MacOS builds".
ideally, a documented next-step / workaround would also be great.