Fix warning in PodLogService when no running pod is found

[rohanKanojia]

We no longer have start and stop goals. Replacing those with deploy
and undeploy

Description

Type of change

• Bug fix (non-breaking change which fixes an issue)
• Feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change
• Chore (non-breaking change which doesn't affect codebase;
  test, version modification, documentation, etc.)

Checklist

• I have read the contributing guidelines
• I signed-off my commit with a user that has signed the Eclipse Contributor Agreement
• I Added CHANGELOG entry
• I have implemented unit tests to cover my changes
• I have updated the documentation accordingly
• No new bugs, code smells, etc. in SonarCloud report
• I tested my code in Kubernetes
• I tested my code in OpenShift

[codecov]

Codecov Report

Merging #284 into master will not change coverage.
The diff coverage is 0.00%.

@@            Coverage Diff            @@
##             master     #284   +/-   ##
=========================================
  Coverage     33.04%   33.04%           
  Complexity     2099     2099           
=========================================
  Files           362      362           
  Lines         18512    18512           
  Branches       2744     2744           
=========================================
  Hits           6117     6117           
  Misses        11664    11664           
  Partials        731      731           

Impacted Files	Coverage Δ	Complexity Δ
...clipse/jkube/kit/config/service/PodLogService.java	0.00% <0.00%> (ø)	0.00 <0.00> (ø)

---

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 8555e05...f619a29. Read the comment docs.

[manusa]

We are assuming that this code will be executed by a Maven invocation (which will not always be true, especially when we add other types of plugins).

We need to find a way to provide meaningful warnings (just like what you did), but that are still compatible with any runtime (Maven, Gradle, JKube-kit standalone...).

So maybe something in the lines of:
No pod is running yet. Are you sure you deployed your app using Eclipse JKube apply/deploy mechanism?
Or did you undeploy it? If so try running the Eclipse JKube apply/deploy tasks again.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities (and 0 Security Hotspots to review)
0 Code Smells

0.0% Coverage
0.0% Duplication

The version of Java (1.8.0_131) you have used to run this analysis is deprecated and we will stop accepting it from October 2020. Please update to at least Java 11.
Read more here