feat: specify the resource requirements for the kaniko pod

[garethjevans]

No description provided.

[garethjevans]

This PR allows the user to specify the limits/requests values for the kaniko pod during a build. Our testing has found this is a more effective way of allowing the cluster to autoscale correctly.

If you're happy with this PR, let me know and I'll get some docs added.

[codecov-io]

Codecov Report

Merging #1683 into master will increase coverage by 0.71%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #1683      +/-   ##
==========================================
+ Coverage    49.8%   50.52%   +0.71%     
==========================================
  Files         180      180              
  Lines        8149     8166      +17     
==========================================
+ Hits         4059     4126      +67     
+ Misses       3708     3658      -50     
  Partials      382      382

Impacted Files	Coverage Δ
pkg/skaffold/schema/latest/config.go	100% <ø> (ø)	⬆️
pkg/skaffold/schema/v1beta7/upgrade.go	66.66% <ø> (ø)	⬆️
pkg/skaffold/build/kaniko/sources/sources.go	89.33% <100%> (+89.33%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e9907a4...324f676. Read the comment docs.

[garethjevans]

@dgageot anything else I need to do on this?

[googlebot]

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

ℹ️ Googlers: Go here for more info.

[googlebot]

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

[tejal29]

ah nvm, ignore the "pkg/webhook/kubernetes/deployment.go" it is something internal for generating docs.

[tejal29]

@garethjevans I discussed this with the team and this looks good!
Since this is a config change, we have to freeze the config.
I am going to get that Pr out and then once that is in, please rebase and this PR will be ready to be merged!!

[tejal29]

@garethjevans Please rebase and this should be ready to merge!

[garethjevans]

@tejal29 the PR has been rebased and is ready to go

contributor has addressed all the concerns