feat(spc-config): Separate resolved and non-resolved functions in spc-config

[crazywhalecc]

What does this PR do?

Checklist before merging

• If you modified *.php or *.yml, run them locally to ensure your changes are valid:
  • composer cs-fix
  • composer analyse
  • composer test
  • bin/spc dev:lint-config

[henderkes]

on the resolved path this acts the same way pgo-v3 does currently, I assume?

[crazywhalecc]

on the resolved path this acts the same way pgo-v3 does currently, I assume?

This change primarily aims to avoid directly modifying config() and breaking the include_suggests option. Internally, we need the resolved result, so a separate method is better. This aligns with the approach in pgo-v3, but the details may differ.

I think we can perform full testing after merging #1214 and before merging this PR, and if there are no issues, continue migrating the changes from pgo-v3 based on this. feat/pgo-v3-split basically includes most of the modifications that are unrelated to spc-config, pgo, and the toolchain.

[github-actions]

StaticPHP Test Bot

Detected: Extensions: rdkafka, swoole | Libraries: krb5, postgresql | Targets: none
Active labels: sapi/frankenphp
Available labels: need-test (gate), test/linux test/windows test/macos (platform), test/tier2 (extra arch), test/php-83 test/php-84 (PHP version), sapi/frankenphp (extra FrankenPHP SAPI build)
Config: Linux x86_64 + Windows x86_64 + macOS arm64 | PHP 8.5 NTS + SAPI: frankenphp (Tier1 Linux/macOS/Windows)