AlgoScan

Replace the boolean `values` query parameter on
GET /v2/applications/{app-id}/boxes with an extensible
`include` string-array parameter (enum: "values"). This
aligns with the existing AccountApplicationsInformation
endpoint pattern and allows future response decorations
without adding new boolean flags.

API spec changes:
- Rename `values` (bool) to `include` (string array,
  enum: ["values"], CSV collection format) in OAS2 and
  OAS3 specs
- Update endpoint description to reference `include`
  instead of `values`

Server changes:
- Update handler to check `slices.Contains(*params.Include,
  "values")` instead of `nilToZero(params.Values)`
- Regenerate all route and model files from updated spec

Client changes:
- Convert `applicationBoxesParams.Values` (bool) field to
  `Include` (string) field in REST client
- Add bool-to-string conversion in ApplicationBoxesPage
  to preserve existing Go function signature

DB query changes:
- Extract duplicate SQL template in sqlitedriver into a
  shared `lookupKeysByRangeTemplate` variable to reduce
  duplication between key-only and key+value queries

Test changes:
- Update all test cases to use
  `[]GetApplicationBoxesParamsInclude{...}` instead of
  `*bool`
- Add UnknownIncludeValueIgnored test verifying that
  unrecognized include values are silently ignored
  (consistent with AccountApplicationsInformation)
- Update comments referencing `values=true` to
  `include=values`

Misc:
- Move TODO comment out of import block in
  util/metrics/reporter.go to satisfy fmt linter