add kaniko builder
add s3 cache for cargo, python

Georgy Moshkin authored 9 months ago and Dmitry Rodionov committed 9 months ago

Previously tests did change environment variables and since they run in
parallel this lead to other tests failing because of unexpected env
content

Co-authored-by: Dmitry Rodionov <d.rodionov@picodata.io>

Close: https://git.picodata.io/picodata/picodata/picodata/-/issues/577

Previously when running `pico.sql [[ create table foo ]]` we would get
this output:
```
---
- null
- "sbroad: rule parsing error:  --> 1:9\n  |\n1 |  create table foo \n  |  ^---\n
  \ |\n  = expected Unique"
...
```

But now the output will be:
```
---
- null
- |+
  sbroad: rule parsing error:  --> 1:9
    |
  1 |  create table foo
    |         ^---
    |
    = expected Unique

...
```

These tests are quire lengthy and are useful only when we changed the
patchset.

So run them always on master, and if `certification_patches` dir
contains any changes. Otherwise use `when: manual`

this fixes the following bug:
```
picodata run --data-dir tmp/i1/
C> invalid socket path: tmp/i1//admin.sock
[supervisor:214288] no ipc message from child
[supervisor:214288] subprocess 214289 exited with code 1
```

We don't need to replace $n with question marks any more, as we support
the pg parameters format.

See https://git.picodata.io/picodata/picodata/sbroad/-/merge_requests/377
and https://git.picodata.io/picodata/picodata/sbroad/-/issues/543.

Виталий Шунков authored 9 months ago and Dmitry Rodionov committed 9 months ago

https://git.picodata.io/picodata/picodata/picodata/-/work_items/563