Clarification on future of incompatible_no_rule_outputs_param

### Page link:

_No response_

### Problem description (include actual vs expected text, if applicable):

Implicit outputs have been deprecated for years: https://bazel.build/rules/lib/globals/bzl.html#rule

This flag has existed since 2018, but is breaking in many projects: https://github.com/bazelbuild/bazel/issues/7977#issuecomment-1246684425

rules_cc doubts that this incompatibility is actually going to happen: https://github.com/bazelbuild/rules_cc/issues/602#issuecomment-3885275565

Clarity as to the future of implicit outputs would help.

### Where do you see this issue? (include link to specific section of the page, if applicable)

_No response_

### Any other information you'd like to share?

_No response_

Review the implicit outputs documentation, the linked Bazel issue comment, and the rules_cc issue to understand the conflicting expectations around incompatible_no_rule_outputs_param. Done means the future behavior and migration expectations are clearly documented or an explicit decision is recorded.

Written by the indexing model from the issue text.