wasm/deps: provide dependencies in bzlmod

[mmorel-35]

Description

Provide dependencies in bzlmod

[phlax]

i think this is currently disabled/broken, otherwise i would say lets make it work bzlmod - but it would also require figuring what broke already

lgtm, thanks @mmorel-35

[phlax]

i take that back - it looks like it is tested/passing here - so then ... would be great to get this testing with bzlmod

[mmorel-35]

This is not related to bzlmod, It is not yet enabled here

[mmorel-35]

It also renames envoy-example-wasmcc to envoy_example_wasmcc to harmonize naming logic accross envoyproxy

[phlax]

It also renames

i prefer kebab-case - was gradually moving them to that - either way lets not rename in this pr

can we get it to actually build with bzlmod?

[mmorel-35]

Not entirely we still need to finish envoy first as it relies on it.
I only test for bazel mod tidy --enable_bzlmod --lockfile_mode=update to pass now

[mmorel-35]

Unintended deletion...

[mmorel-35]

Shall all modules be named with kebab-case and keep them as repo_name with actual name until new name is used everywhere ?

modules : envoy-api, envoy-examples, envoy-example-wasmcc, envoy-mobile, envoy-build-config, envoy-toolshed
repo_names: envoy_api, envoy_examples, envoy_mobile, envoy_build_config, envoy_toolshed

[mmorel-35]

/retest

[phlax]

sorry - i missed your question here - i was just meaning the examples - and in particular their filepath - which is used in envoy's docs etc

i think for bzlmod we should go with the snake case convention that most others seem to use

[mmorel-35]

Alright I fixed it in toolshed, examples and envoy

[mmorel-35]

/retest