ci/Tests: use a container image to avoid installing klayout in each job

[umarcor]

Fixes #30

/cc @atorkmabrains

[mithro]

This pull request needs to be rebased before we can merge.

[atorkmabrains]

@mithro this rebase and merge process will be extremely painful process due to the long standing PR list. We will have to redo many many times. Please give me admin access on this repo to finalize all changes.

[proppy]

is the image public?

[umarcor]

The image is neither public nor private, because it's not pushed to any registry. It's built in one step and used in the next step, both of them executed within the same job. Therefore, the name might be anything; it's local only.

However, it might make sense to eventually split building the image and using it, in order to avoid installing the dependencies in each job. That's what #55 is about.

[proppy]

ah make sense, curious if you consider caching it with docker save/load instead?

[proppy]

@mithro this rebase and merge process will be extremely painful process due to the long standing PR list

It shouldn't be a problem to rebase this change, it looks like the only other PR affecting .github/workflows/Tests.yml is #55 and it's still a draft.

[atorkmabrains]

@proppy The name change PRs are very extensive. We will have to do the rebase and merge many many times.

[proppy]

We will have to do the rebase and merge many many times.

I believe that github only mandate a rebase when it detect a conflict, see https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github

[atorkmabrains]

@proppy I know that. Name change will definitely create conflicts. This a major change and work that I want to avoid.

[umarcor]

Closing per #30 (comment).

[atorkmabrains]

Thanks @umarcor Appreciate your work. Was really helpful.