Global `const` symbols not resolved within action/parser bodies

const symbols defined in the global scope do not seem to be usable for reads/writes within parser bodies or actions, as below:

const bit<16> GENEVE_OPT_CLASS_OXIDE = 16w0x0129;

control x (
    /* ... */
) {
    action y (
        inout headers_t hdr,
        /* ... */
    ) {
        hdr.ox_external_tag.class = GENEVE_OPT_CLASS_OXIDE;
    }

    /* ... */
}

This produces the following error message:

error: could not resolve lvalue: GENEVE_OPT_CLASS_OXIDE
    GENEVE_OPT_CLASS_OXIDE not found
[361:37] sidecar-lite.p4

          hdr.ox_external_tag.class = GENEVE_OPT_CLASS_OXIDE;
                                      ^^^^^^^^^^^^^^^^^^^^^^

From my testing, this also applies to use of constants within expressions in parser states.

Start by reproducing the P4 example with the global const used in an action, then check the corresponding parser-state expression case. Trace name resolution for reads and writes from parser bodies and actions; done means both uses resolve without the reported lvalue error.