Packages: Pass CFLAGS to compile wasm modules on all packaging targets

[thresheek]

This extends the approach used for debian-based packages in 3f805bc to rpm as well. Notable change for both deb and rpm packaging is to use CFLAGS as defined in the build/Makefile, and not pass them from the environment which might not be there (as is the case for rpm).

While at it, stop passing CFLAGS in the install phase, as it should no longer invoke builds (see d54af16).

The rpm part was overlooked in 7a64055, since testing was not done on the platforms where problem manifested itself, notably Amazon Linux 2023 and Fedora 38+.

[thresheek]

Fixed wrong target in rpm for make install (wasm-install instead of wasm)

git range-diff --no-color 17a2618...52f5a7e
1:  17a26184 ! 1:  52f5a7e2 Packages: Pass CFLAGS to compile wasm modules on all packaging targets
    @@ pkg/rpm/Makefile.wasm: MODULE_VERSION_wasm=      $(VERSION)

      MODULE_CONFARGS_wasm=     wasm --include-path=\`pwd\`/pkg/contrib/wasmtime/crates/c-api/include --lib-path=\`pwd\`/pkg/contrib/wasmtime/target/release \&\& ./configure wasm-wasi-component
     -MODULE_MAKEARGS_wasm=     wasm wasm-wasi-component
    --MODULE_INSTARGS_wasm=     wasm-install wasm-wasi-component-install
     +MODULE_MAKEARGS_wasm=     wasm wasm-wasi-component CFLAGS=\"\$$(grep ^CFLAGS build/Makefile | cut -d' ' -f 3-) -Wno-missing-prototypes\"
    -+MODULE_INSTARGS_wasm=     wasm wasm-wasi-component-install
    + MODULE_INSTARGS_wasm=     wasm-install wasm-wasi-component-install

      MODULE_SOURCES_wasm=
    -

[ac000]

Heh, all the wasm's merge together... ;)