feat(pricing): add AWS Price List Service support

[ShubhamDX]

Summary

Adds the AWS Price List Service (pricing:* / AWSPriceListService.*) emulation — the stateless prerequisite for the Cost Explorer and CUR services proposed in #791.

• Five operations: DescribeServices, GetAttributeValues, GetProducts, ListPriceLists, GetPriceListFileUrl
• JSON 1.1 protocol, reuses existing AwsJson11Controller dispatch
• Backed by a bundled classpath snapshot; override via FLOCI_SERVICES_PRICING_SNAPSHOT_PATH for custom datasets
• Pagination with Base64 offset tokens (AWS-compatible shape)
• PriceList returned as array-of-JSON-strings — matches real wire format so SDKs parse offers directly

Why

Per scope discussion in #791, this is PR 1 of 3. FinOps tooling (cost detection, budget guards, CUR parsers, anomaly detectors) can't currently run against Floci because the billing APIs are absent. Pricing is the smallest stateless piece and unblocks the next two PRs (ce:*, cur:*).

Design choices

• Bundled snapshot (minimal). AmazonEC2, AmazonS3, AWSLambda in us-east-1 only. Keeps the image small; users wanting full coverage drop a Price List bulk download under FLOCI_SERVICES_PRICING_SNAPSHOT_PATH.
• No new dependencies. Snapshot is plain JSON, parsed with the existing Jackson mapper.
• No SPI. Cost-synthesis / pluggability deferred until a second consumer emerges — keeps scope minimal per the existing stateless pattern.
• Path-safe snapshot loader. Segment-level validation on any input used to build a filesystem path (ServiceCode, AttributeName, regionCode), plus root-containment check in SnapshotLoader so the override directory can't be escaped.
• EffectiveDate accepts both wire shapes. AWS JSON spec uses Unix epoch seconds (number); the handler also accepts ISO-8601 strings for SDK/CLI variance.

Test plan

• ./mvnw test -Dtest=PricingIntegrationTest — 26/26 green locally (Java 25)
• Wire-format assertions for each operation via RestAssured against a booted @QuarkusTest instance
• Validation-error paths (ValidationException, InvalidParameterException, UnknownOperationException)
• Filter matching, filter input validation (missing Field/Value), pagination round-trip
• EffectiveDate version selection (numeric epoch + ISO-8601, with multi-version AmazonEC2 us-east-1 fixture)
• Path-traversal rejection on AttributeName and regionCode
• CI to run the full suite

Scope boundaries (out of scope for this PR)

• CE / CUR / BCM Data Exports — will land as separate PRs per the scope thread in Proposal: add AWS Cost Explorer / CUR / Pricing API surface #791.
• Bulk download of full regional price lists (GetPriceListFileUrl returns a stub URL).
• Savings Plans / Reserved Instance pricing terms beyond the bundled snapshot.

Refs: https://github.com/orgs/floci-io/discussions/791

[ShubhamDX]

For reviewer context — this is PR 1 of the 3-PR scope discussed in #791. Tracking issues for the remaining two:

• feat: add Cost Explorer (ce:*) service #822 — Cost Explorer (ce:*) service (consumes this PR's Pricing snapshot)
• feat: add CUR + BCM Data Exports services #823 — CUR + BCM Data Exports services (consumes the CE synthesis from feat: add Cost Explorer (ce:*) service #822)

Each PR is independently reviewable; this one does not depend on the others landing.

[ShubhamDX]

Marked this ready for review. CI workflows are sitting in action_required state - looks like the first-time-contributor approval gate. Waiting on a maintainer to click "Approve and run". Happy to address anything CI flags.

[hectorvent]

Thanks @ShubhamDX

[cfranzen]

I tried to use this service from testcontainers and there seems to be an issue with the PricingService.load() method. It looks to me as if this method is never called when running Floci as container. I can't see any log output from the PricingService in the logs and the load() method should always log some information. When calling the pricing service via the API, there seem to be no service codes available.

[ShubhamDX]

Thanks for the report @cfranzen — confirmed: the bundled pricing-snapshots/** tree was missing from the native-image build, so the standard container had no JSON files to read. load() returns silently before logging because the classpath lookup returns null rather than going down the WARN path.

Hotfix up at #836: registers the tree under quarkus.native.resources.includes and switches to the class's own classloader (the thread-context loader can be the bootstrap loader in a native image and miss application resources). Should restore the service-code list in the container build.

[ShubhamDX]

@cfranzen — verified the fix locally against the native build (full log on #836). DescribeServices now returns the expected three services (AmazonEC2, AmazonS3, AWSLambda) and GetProducts returns rate data. The missing Pricing snapshot loaded log line is now present in the container output, confirming @PostConstruct runs as intended.

[ShubhamDX]

@cfranzen — thanks again for catching this. The original PR was working on the JVM image (and all the tests in PricingIntegrationTest pass under ./mvnw test, which boots Quarkus on the JVM), so the snapshot loader looked fine in CI. The bug was specific to the GraalVM native binary that ships in the standard floci/floci:latest image, which is what Testcontainers pulls by default.

Two GraalVM-only failures combined:

1. Resource bundling. Quarkus's static resource analysis only includes classpath resources it can prove are read. The pricing snapshot path is built dynamically ("pricing-snapshots/" + relativePath), so GraalVM stripped every JSON file out of the native image. On the JVM the files are still on the classpath, so the loader worked.
2. Classloader. Thread.currentThread().getContextClassLoader() returned the bootstrap loader inside the native image, which doesn't see application resources. On the JVM it returns the application loader, so even without (1) the read would have succeeded.

Fix in #836:

• Register pricing-snapshots/** under quarkus.native.resources.includes so GraalVM bundles the tree.
• Read via PricingService.class.getClassLoader() so the same code path works on JVM and native.

Verified locally with docker build -f docker/Dockerfile.native + container run — DescribeServices now returns the expected three services and the missing Pricing snapshot loaded log line shows up. Full evidence on #836.