Friction log: Running `skaffold dev` on triage party.

This is the FL for running `skaffold dev` on a single container app

Set up
1. Checkout https://github.com/google/triage-party
3. Set up secret in namespace. (might have to create namespace before)
```
kubectl create secret generic triage-party-github-token --from-file=token=$HOME/.github-token --namespace triage-party

```
2. Run `skaffold dev -d gcr.io/your-repo`

Summary of Issues
- [ ] Logs from pod don't show up in skaffold dev
- [ ] Manual deploy triggers don't work when you want to trigger a re-deploy when previous deployment failed due to "connectivity" or "secret not found" and dev is watching for changes.
- [ ] Did not realize, image defined in `skaffold.yaml` was not deployed. No warnings!

Initial issue for which i created this issue for.

On triage party with skaffold built on head, logs for pods deployed in a namespace are not showing up.

```
triage-party git:(add_planning_board) ✗ skaffold dev -d gcr.io/tejal-gke1
Listing files to watch...
- tparty
Generating tags...
- tparty -> gcr.io/tejal-gke1/tparty:latest
Checking cache...
- tparty: Found Remotely
Starting test...
WARN[0004] Ignoring image referenced by digest: [gcr.io/tejal-gke1/tparty:latest@sha256:86ba1f8274ba42761f22aada6d594d891061c2cfc4e8ded14a5551f85cbd0f69]
Tags used in deployment:
- tparty -> gcr.io/tejal-gke1/tparty:latest@sha256:86ba1f8274ba42761f22aada6d594d891061c2cfc4e8ded14a5551f85cbd0f69
Starting deploy...
- namespace/triage-party configured
- configmap/triage-party-config configured
- deployment.apps/triage-party configured
- service/triage-party configured
Waiting for deployments to stabilize...
- triage-party:deployment/triage-party is ready.
Deployments stabilized in 5.054 seconds
Press Ctrl+C to exit
Watching for changes...
Port forwarding Service/triage-party in namespace triage-party, remote port 8080 -> 127.0.0.1:8080

```

To check logs, i need to
```
kubectl logs po/triage-party-5d6fb99b5f-hhl7s -n triage-party -f

```