[Log]: honor global LogParameters/NoLog when aspect comes from Apply rule

[MistyKuu]

The [Log] source generator had two resolution holes that silently let
parameter values through even when the user asked for them to be redacted:

1. LogClassDataProvider.ExtractClassData only returned defaults if the
   class had a method-level [Log] attribute, so global settings like
   ILogConfigurator.Defaults(d => d.LogParameters = false) were dropped
   whenever [Log] was applied via b.Apply(...) or a
   class-level [Log]. The emitter then fell back to the hardcoded true.

2. ParseInterfaceProxy built the method model from openMethod.Parameters,
   so [NoLog] / [Sensitive] / [return: NoLog] declared on the concrete
   impl were invisible to the synthesized interface proxy. Calls made
   through the interface reference logged data the impl had redacted.

Fixes:

• LogClassDataProvider now also detects class-level [Log] and any method
  matched by an Apply rule in IAopConfigurator.
• BuildMethodModel, CollectAspects and CollectVirtualAspect accept an
  optional attributeOverlay method; ParseInterfaceProxy passes the
  resolved impl so its parameter and return-type attributes are unioned
  with the interface's own.
• Documented resolution order (method > class > Apply-config > global
  Defaults > hardcoded) in a CollectAspects doc comment.

Tests cover Apply(selector, configure) with LogParameters=false, and
[NoLog] on both the interface and impl parameter when dispatched through
the interface.

https://claude.ai/code/session_01AgEzrm85raXE4PpBueGsbM