`UNRESOLVED_ENV_VAR` reported when add external rust file with `include!`

The code is at repo for reproduce, you can build it with

BINDING_PATH=../../build/bindings.rs cargo build --manifest-path ./proj/Cargo.toml

However when editing in VSCode, rust-analyzer report UNRESOLVED_ENV_VAR on the include! macro:

I think I already set necessary variables in the settings.json

{
    "rust-analyzer.cargo.extraEnv": {
        "BINDING_PATH": "${workspaceFolder}/build/bindings.rs"
    },
    "rust-analyzer.check.extraEnv": {
        "BINDING_PATH": "${workspaceFolder}/build/bindings.rs"
    },
    "rust-analyzer.restartServerOnConfigChange": true,
}

How can I eliminate this error and enable IntelliSense for the bindings crate?

rust-analyzer version: rust-analyzer version: 0.3.2029-standalone

rustc version: rustc 1.79.0 (129f3b996 2024-06-10)

editor or extension: VSCode

relevant settings: null

repository link (if public, optional): repo for reproduce

code snippet to reproduce:
You can find the code at the repository above

Start with the linked fre3dm4n/rust-analyzer-issue repository and reproduce the report using the documented BINDING_PATH and cargo build command. Then trace how rust-analyzer handles include! environment variables and the cargo.extraEnv/check.extraEnv settings; done means the false UNRESOLVED_ENV_VAR diagnostic is eliminated and IntelliSense works for the bindings crate.