[python] use posix-compatible dot instead of bashism source (jetify-c…

…om#1699)

## Summary

Think its a bit nice to be posix compatible where we can.

The downside is that `source` is more recognizable, perhaps, compared to
`dot`.

## How was it tested?

cicd tests

0.8.5 Release

[envsec] Enforce version (jetify-com#1688)

## Summary

Previously we didn't want to enforce a version because it requires a
code change for every new version, but while testing this is good
because it forces everyone to the same version of envsec. (in the future
we won't use the envsec binary at all, so the version will be tightly
coupled anyway)

Don't merge this until v0.0.13 is actually created 

## How was it tested?

[plugins] fix info for packages with process-compose services (jetify…

…-com#1689)

## Summary

We were relying on the package already being installed and in virtenv.
This change ensures it works when not installed as well.

## How was it tested?

`devbox info php`

[Renaming] ComputeNixEnv -> ComputeEnv; ensurePackagesAreInstalled ->…

… ensureStateIsCurrent (jetify-com#1675)

## Summary

These names were getting rather stale. Hopefully, the new ones represent
them more accurately.

## How was it tested?

compiles and cicd tests should pass

0.8.4 Release

[launcher] Bump launcher version (jetify-com#1670)

## Summary

Depends on jetify-com/axiom#3577

(that needs to be deployed before this change can be released)

## How was it tested?

0.8.3 Release

 [docker] security fix of sudo/chown/user issue jetify-com#1638 (jeti…

…fy-com#1639)

## Summary
Potential fix of mentioned security issue:
jetify-com#1638

## How was it tested?
devbox generate dockerfile
docker build -t devbox-test .
docker run -it devbox-test

---------

Co-authored-by: John Lago <750845+Lagoja@users.noreply.github.com>

[auth] Update auth package (jetify-com#1647)

## Summary

## How was it tested?