pasit_test: Use passport container name to avoid Satlab port conflict

Newer Satlab builds start a container named passport at boot that binds
host port 8300, causing pasit_test to fail with a port conflict when
starting a second container named passport-dev on port 8300.

Switch PASSPORT_CONTAINER to passport (while still cleaning up any
leftover passport-dev container) and match the exact container name in
docker ps checks so image names do not trigger false positives.

BUG=b:584402507
TEST=Verified pasit_test -p -- -h failed before fix and passes with fix applied on satlab-bld4

Change-Id: I5fffe86d91397303553ad7838dfd22f5433873d3
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/satlab/+/8797997
Auto-Submit: Brett Brotherton <bbrotherton@google.com>
Tested-by: Brett Brotherton <bbrotherton@google.com>
Reviewed-by: Przemysław Filipek <filipek@google.com>
Commit-Queue: Przemysław Filipek <filipek@google.com>