CPU requests change to `0` when limits introduced.

[varditn]

When setting k8s resources limits on AS pod that doesn't have requests configured manually, CPU requests change to 0 from the default 1 value.

resources:
    limits:
      cpu: 1300m
      memory: 1395864371200m
    requests:
      cpu: "0"
      memory: 1Gi

[pires]

Yep, this was a bug introduced in #5. Basically, when computing requests the code evaluates if cpu and memory are set (each on their own function) by ensuring it's not nil when it should also ensure it's not zero.
Interestingly enough, the correct validation was implemented for limits. @FlavioF this should be trivial for you to fix. I recommend you add tests that cover the failure you are observing to ensure it never happens again :)