Add pod resource with no status check implemented.

[tejal29]

Relates to #176

Description

User facing changes

Write n/a if not output or log lines changed and no behavior is changed

Before

If log/output changes: Paste the current relevant skaffold output
If behavior changes: describe succinctly the current behavior

After

If log/output changes: Paste skaffold output after your change
If behavior changes: describe succintly the behavior after your change

Next PRs.

In this section describe a list of follow up PRs if the current PR is a part of big feature change.

See example #2811

Write n/a if not applicable.

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

• [X ] Includes unit tests
• [ X] Mentions any output changes.
• [ n/a] Adds documentation as needed: user docs, YAML reference, CLI reference.
• [ n/a] Adds integration tests if needed.

See the contribution guide for more details.

Double check this list of stuff that's easy to miss:

• If you are adding a example to the examples dir, please copy them to integration/examples
• Every new example added in integration/examples dir, should be tested in integration test

Reviewer Notes

• The code flow looks good.
• Unit test added.
• User facing changes look good.

Release Notes

Describe any user facing changes here so maintainer can include it in the release notes, or delete this block.

Examples of user facing changes:
- Skaffold config changes like
  e.g. "Add buildArgs to `Kustomize` deployer skaffold config."
- Bug fixes
  e.g. "Improve skaffold init behaviour when tags are used in manifests"
- Any changes in skaffold behavior
  e.g. "Artiface cachine is turned on by default."

[codecov]

Codecov Report

Merging #2928 into master will increase coverage by 0.03%.
The diff coverage is 100%.

Impacted Files	Coverage Δ
pkg/skaffold/deploy/resource/pod.go	100% <100%> (ø)

[priyawadhwa]

lgtm, just one nit