Support response based impression registration with AttributionSrc Url

### Description

Chrome proposed a new way for impression registration with the use of the AttribtionSrc Url ([explainer](https://developer.chrome.com/docs/privacy-sandbox/attribution-reporting-changes-january-2022/#header-source-event-how)).

With this proposal, we need to send a separate ping to fetch the attribution source for eligible traffic meeting the following conditions:
- attribution reporting is enabled
- there is `ase=1` (attribution-source-enabled) Url param in the tracking Url

The new attribution source Url will be modified from the existing tracking Url by injecting the `asr=1` (attribution-srouce-request) into it so that the recipient click servers can distinguish it.

### Alternatives Considered

Successor of https://github.com/ampproject/amphtml/issues/35347

### Additional Context

_No response_

No files, tests, or entry points are named in the issue. Start by locating AMP's attribution-reporting tracking-URL handling and impression-ping code, then trace how the ase=1 parameter is detected. Done means eligible traffic sends the separate attribution-source request with asr=1 while preserving the stated conditions.

Written by the indexing model from the issue text.