refactor: restructure with lockup dir

[andreivladbrg]

Closes #10, #11, #13

Important

The merge of this PR should be synchronized with renaming this repo to deployments (removing "V2") and updating the documentation in places such as this

[smol-ninja]

Renaming this repo to deployment can be synchronised with renaming v2-core to lockup. So, feel free to merge this and open another issue about renaming repo.

[andreivladbrg]

So, feel free to merge this and open another issue about renaming repo.

we need to also update the hyperlinks in docs

[smol-ninja]

Right. So should we mark it as draft then to prevent accidental merging of this PR

[andreivladbrg]

Right. So should we mark it as draft then to prevent accidental merging of this PR

we could, but some clarifications, doesn't "draft" mean that the work for the individual PR is not finished?
the case here is that for deployments PR is finished, but we need to updated other repos

[smol-ninja]

As per https://github.blog/news-insights/product-news/introducing-draft-pull-requests/, Draft PR can be used to send various signals one of which is to block merging the pull request.

[smol-ninja]

Here is another review after merging #14.

1. ZKsync broadcasts and ZKsync artifacts are missing. ZKsync artifacts should be different because of hardhat requirement (similar to lockup directory).
2. We should update the Scripts section in the README file as the bash scripts are no longer used to make deployments.
3. Link to Flow npm package was missing from README which I have added in 61e0b2f.

[andreivladbrg]

ZKsync broadcasts

unfortunetely i didn't have them this time, i don't know why

ZKsync artifacts are missing

will add them

[smol-ninja]

LGTM.

[smol-ninja]

Should we merge it @andreivladbrg given we are going live in a few hours? We will then have to update the links in docs as well.