pio.AssemblerV0 implemented and tested on CYW43439

[soypat]

New Assembler tested with CYW43439

➜  cyw43439 git:(lneto-stack) go work init                           
➜  cyw43439 git:(lneto-stack) go work use . ../pio     
➜  cyw43439 git:(lneto-stack) tinygo flash -target=pico -monitor ./examples/dhcp
Connected to /dev/ttyACM0. Press Ctrl-C to exit.
starting program
time=1970-01-01T00:00:02.009Z level=INFO msg=Init:start
time=1970-01-01T00:00:03.502Z level=INFO msg=Init:done took=1.492372s
time=1970-01-01T00:00:03.503Z level=INFO msg=joinWpa2 ssid=Patoniato len(pass)=15
time=1970-01-01T00:00:06.946Z level=INFO msg=rxEvent event=AUTH status=0 reason=0 flags=0 dev.linkstate=1
time=1970-01-01T00:00:06.947Z level=INFO msg=rxEvent event=SET_SSID status=0 reason=0 flags=0 dev.linkstate=2
Retrying DHCP
1970/01/01 00:00:15 ERROR stackudp:demux err="dcpv4 unexpected state in recv bound"
time=1970-01-01T00:00:15.174Z level=ERROR msg=tryPoll:rx plen=0 err="dcpv4 unexpected state in recv bound"
time=1970-01-01T00:00:16.193Z level=INFO msg="DHCP complete" hostname=DHCP-pico ourIP=192.168.1.60 subnet=192.168.1.0/24 router=192.168.1.1 server=192.168.1.1 broadcast="invalid IP" gateway=0.0.0.0 gatewayhw=e8:4d:74:9f:61:4a lease[seconds]=86400 rebind[seconds]=0 renew[seconds]=0 DNS-servers=[192.168.1.1]

[soypat]

The version tagging ain't pretty, I know, but hardware is hardware. I'd rather have pio.AssemblerV0 and pio.AssemblerV1 than pioasmv0.Assembler and pioasmv1.Assembler

[deadprogram]

Understood, it is probably the least bad option. Now merging.