Drop non-BC-safe block_content\Access renames from default set
### Problem/Motivation
Removes block_content\Access → Core\Access renames from the default drupal-11.3-deprecations set since Core\Access homes only exist on 11.3.0+ and cannot be BC-wrapped. Renames are kept in the opt-in DRUPAL_113_BREAKING set.
### Work items
- Commit(s): [bd97b5b5af](https://github.com/palantirnet/drupal-rector/commit/bd97b5b5af1f)
### Credit
- Implemented by: @bbrala
---
*Filed retroactively as part of the Drupal 12 rector coverage effort. Closed as fixed; credit to be applied to the contributors listed above.*
*AI was used extensively to build this fix and to file this issue. See [Dries Buytaert: AI-generated Rector rules for Drupal](https://dri.es/ai-generated-rector-rules-for-drupal) and [Björn Brala: Drupal Rector rules are config, not code. Mostly.](https://www.linkedin.com/pulse/drupal-rector-rules-config-code-mostly-bj%C3%B6rn-brala-vfpwe/).*
issue