You can warn, but you cannot completely forbid

### What is this about?

I am a developer, i frequently transfer tokens to contract,

in the past, metamsk only warn, but now it completely forbid, and warn: This address is a token contract address. If you send tokens to this address, you will lose them.

I can not continue, and i find settings without findings solutions.

any one can help

### Scenario

_No response_

### Design

_No response_

### Technical Details

_No response_

### Threat Modeling Framework

_No response_

### Acceptance Criteria

_No response_

### Stakeholder review needed before the work gets merged

- [ ] Engineering (needed in most cases)
- [ ] Design
- [ ] Product
- [ ] QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
- [ ] Security
- [ ] Legal
- [ ] Marketing
- [ ] Management (please specify)
- [ ] Other (please specify)

### References

_No response_

Start by reproducing the token transfer to a contract address and inspect the available settings related to MetaMask's warning or blocking behavior. No files, tests, technical details, or acceptance criteria are provided; completion depends on establishing the intended behavior and verifying it in the transfer flow.

Written by the indexing model from the issue text.