fix: copy pubspec.yaml to secondary folder in virtual env

[murali-shris]

- What I did

• fixed version issue in virtual env
  - How I did it
• copied pubspec.yaml to secondary folder in virtual env setup
  - How to verify it
• TBD

[cpswan]

I don't think this will work, as there isn't a pubspec.yaml in the source directory, and we don't want to have one in the ve_base.

I'll take a look at what's needed to copy the pubspec.yaml into place when we build a ve image.

[cpswan]

This looks like the culprit:

~/git/github.com/atsign-foundation/at_server/tests/at_functional_test/lib/secondary/base$ ls -la
total 8
drwxr-xr-x 2 chris chris 4096 Oct 27 08:36 .
drwxr-xr-x 3 chris chris 4096 Oct 27 08:36 ..
lrwxrwxrwx 1 chris chris   57 Oct 27 08:36 pubspec.yaml -> ../../../../at_secondary/at_secondary_server/pubspec.yaml

We have a symlink that's been messed up by the recent directory moves.

But that would affect VE in at_functional_tests, not in the atsigncompany/virtualenv:dev_env image.