docs(pc0038,fc0007,lc0089) Document shared flow-terminating built-ins across rules

[MODUSCarstenScholling]

Summary

Document shared flow-terminating built-ins across PC0038, FC0007, and LC0089.

This documentation change accompanies ALCops/Analyzers#505, which implements the described behavior.

Changes

PC0038

• Explain that return values are required only on reachable paths.
• Document named-return assignment tracking in conditions, case selectors, loop expressions, for bounds, and foreach collections.
• Document exhaustive enum and option case handling.
• Document terminating built-in calls:
  • Error(...)
  • Record.FieldError(...)
  • FieldRef.FieldError(...)
• Clarify that user-defined procedures named Error or FieldError do not terminate a path.

FC0007

• Document Record.FieldError(...) and FieldRef.FieldError(...) as scope-leaving statements for ErrorOnly and ExitAndError.
• Clarify that scope-leaving spacing applies only to the supported built-in calls.
• Keep direct if-branch behavior unchanged: branch statements are not sibling statements for FC0007 spacing analysis.

LC0089

• Document Error(...), Record.FieldError(...), and FieldRef.FieldError(...) as guard-clause exits.
• Explicitly document the supported report and XMLport guard exits:
  • CurrReport.Break()
  • CurrReport.Skip()
  • CurrReport.Quit()
  • CurrXMLport.Break()
  • CurrXMLport.Skip()
  • CurrXMLport.Quit()
• Clarify that CurrReport and CurrXMLport methods are Cognitive Complexity guard exits only; they are not general procedure terminators.
• Clarify that user-defined Error and FieldError methods remain normal calls.

Known limitation

Error(ErrorInfo) is currently documented as flow-terminating even when ErrorInfo.Collectible is true and execution happens inside an ErrorBehavior::Collect scope.

AL can continue after a collectible error in that context. Identifying this precisely requires data-flow analysis of the ErrorInfo value and surrounding collection behavior, which is outside the current invocation-level analysis.

Dependency

Depends on ALCops/Analyzers#505. Merge the analyzer implementation before releasing documentation that describes this behavior.

Replaces existing #153