feat(frontend): add support for wires to concrete-python

[aPere3]

closes https://github.com/zama-ai/concrete-internal/issues/715

[github-actions]

Benchmark

Benchmark suite	Current: 494a5fc	Previous: 66d70b7	Ratio
v0 PBS table generation	60218721 ns/iter (± 302809)	59802486 ns/iter (± 1213879)	1.01
v0 PBS simulate dag table generation	38003941 ns/iter (± 284418)	37033984 ns/iter (± 287177)	1.03
v0 WoP-PBS table generation	68112466 ns/iter (± 511478)	67839950 ns/iter (± 436131)	1.00

This comment was automatically generated by workflow using github-action-benchmark.

[BourgerieQuentin]

Looks good to me, I'm just think that the default composition of modules should be fully composable as the previous behavior. wdyt?

[umut-sahin]

the default composition of modules should be fully composable as the previous behavior

I don't think we should do this by default. There is a reason why we introduced wires, it's more optimal, and it should be the default choice.

[umut-sahin]

Python side looks good to me, only a few comments. Though I'd love to see the initial wire API we designed as well, it looks much better to me!

[BourgerieQuentin]

the default composition of modules should be fully composable as the previous behavior

I don't think we should do this by default. There is a reason why we introduced wires, it's more optimal, and it should be the default choice.

For me FullyComposable should be the default one, as it make things works then you optimize it using wiring. Then it is the previous behavior so we don't break the legacy.

[aPere3]

For me FullyComposable should be the default one, as it make things works then you optimize it using wiring. Then it is the previous behavior so we don't break the legacy.

Agreed. I changed it this way.