Sync upstream v11.1.2 (merge conflicts)

[JOY (JOY)]

Upstream Sync - v11.1.2

Auto-merge with upstream v11.1.2 failed. Version/workflow conflicts were auto-resolved,
but the following files have code conflicts that need manual resolution:

docker-compose/envs/common-blockscout.env

To resolve:

1. Check out this branch locally
2. Resolve remaining conflicts
3. Push and merge this PR
4. Then create tag v11.1.2 to trigger Docker build

Upstream release notes

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[gemini-code-assist]

Code Review

This pull request introduces comprehensive OpenAPI specifications for the advanced filters and Arbitrum-related endpoints, migrating parameter parsing from string keys to atom keys due to CastAndValidate integration. It also adds extensive agent documentation, scripts, and SPDX license identifiers across the codebase. Key feedback highlights a potential runtime error in the Arbitrum controller where an integer height is passed to a function expecting a string, a potential schema validation failure due to the removal of address_hash from the block rewards schema, and a missing fallback clause in list_methods/2 when the optional query parameter q is absent.

[gemini-code-assist]

The height parameter is cast to an integer by CastAndValidate because its OpenAPI schema type is :integer. However, calculate_celestia_data_key/2 expects height to be a string (binary), as it was passed directly as a string in the original implementation. Passing an integer will cause a runtime error. Convert height to a string using to_string/1 before passing it to calculate_celestia_data_key/2.

  def batch_by_celestia_da_info(
        conn,
        %{transaction_commitment: transaction_commitment, height: height} = _params
      ) do
    with {:ok, :hash, transaction_commitment_hash} <- parse_block_hash_or_number_param(transaction_commitment) do
      key = calculate_celestia_data_key(to_string(height), transaction_commitment_hash)

[gemini-code-assist]

Removing address_hash from the @rewards_schema properties while the view still renders it will cause schema validation failures in tests due to additionalProperties: false. If the view still outputs the recipient's address hash, address_hash must be retained in the schema properties.

[gemini-code-assist]

Since q is an optional parameter, calling list_methods/2 without q (or when q is nil) will result in a FunctionClauseError because the only defined clause requires q to be a binary. A fallback clause should be defined to handle the case when q is absent or nil.