Add centralized deprecation #7302

New Feature / Enhancement Checklist

• I am not disclosing a vulnerability.
• I am not just asking a question.
• I have searched through existing issues.

Current Limitation

Currently, there is no mechanism provided to deprecate Parse Server settings. With the shift to phased deprecation as part of the larger implementation of fixed release cycles, it is not clear how to communicate deprecations.

Feature / Enhancement Description

Introduce a centralized Deprecator that standardizes warning logs for deprecated Parse Server options. This should also make it easy for contributors to identify deprecations to adapt contributions accordingly, and for example not build on top of a feature without knowing that it will be deprecated.

Example Use Case

The option directAccess default should change from false to true in #6636.