The "global" consent enablement has been removed, so we no longer have consent.json. Existing deployments that have consent.json do not need to remove it - the file will be ignored.
Consent is now determined only on a per-mapping, per-object basis (which was already required with the global consent enablement.
See this PR for more info.
Remove the consent.json file from the Self-Service Guide, and add this change to the Compatibility section of the Release Notes.