Sync upstream v11.1.1 (merge conflicts)

[JOY (JOY)]

Upstream Sync - v11.1.1

Auto-merge with upstream v11.1.1 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.1 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 a comprehensive OpenAPI specification framework, including a new inspector agent, detailed authoring skills, and extensive annotations for the Advanced Filter and Arbitrum controllers. It also standardizes parameter handling by migrating to atom-keyed maps via the CastAndValidate plug. Several critical issues were identified in the AdvancedFilterController, including potential runtime crashes due to strict pattern matching on optional parameters, a missing module attribute that would prevent compilation, and a pagination bug where an atom key is passed instead of a required string key.

[gemini-code-assist]

Passing :items_count as an atom key to next_page_params/5 will likely break the cumulative item count in pagination. The standard BlockScoutWeb.Chain.next_page_params/5 helper expects string keys in the extra_params map. Using an atom key here will result in the helper failing to find the existing count, causing it to reset to 0 on every page.

      next_page |> next_page_params(advanced_filters, %{"items_count" => params[:items_count]}, false, &paging_params/1)

[gemini-code-assist]

The list_methods/2 action now strictly matches on the presence of the q parameter. Since q is defined as optional in the OpenAPI spec, a request without this parameter will result in a FunctionClauseError. A fallback clause should be added to handle the default case as described in the endpoint documentation.

[gemini-code-assist]

The module attribute @methods_filter_limit does not appear to be defined in this module based on the provided diff. This will cause a compilation error. Please ensure it is defined, likely near the other method-related attributes at the top of the file.

[gemini-code-assist]

The strict map pattern match in paging_options/1 will cause a FunctionClauseError when any of the optional pagination parameters are missing from the request. Since CastAndValidate does not populate missing optional parameters in the atom-keyed map, this function should handle partial maps or use Map.get/3.

  defp paging_options(params) do
    block_number_string = params[:block_number]
    transaction_index_string = params[:transaction_index]
    internal_transaction_index_string = params[:internal_transaction_index]
    token_transfer_index_string = params[:token_transfer_index]
    token_transfer_batch_index_string = params[:token_transfer_batch_index]