KubernetesSlave#readResolve should call super implementation

[Vlatombe]

As I understand it, this caused KubernetesSlave#nodeProperties to be null after a restart instead of returning an empty list.

Could not reproduce it via RestartPipelineTest maybe because RestartableJenkinsRule is not realistic.

Testing done

Submitter checklist

Preview Give feedback

1. Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
2. Ensure that the pull request title represents the desired changelog entry
3. Please describe what you did
4. Link to relevant issues in GitHub or Jira
5. Link to relevant pull requests, esp. upstream and downstream changes
6. Ensure you have provided tests - that demonstrates feature works or fixes the issue

[jglick]

https://github.com/jenkinsci/jenkins/blob/ae74db6cf1945c57a4ecc4ae4273a9c924f19429/core/src/main/java/hudson/model/Slave.java#L587-L592 OK. Did you try JenkinsSessionRule? But either that or RestartableJenkinsRule should work to reproduce this sort of issue, provided of course that you can arrange for an agent to stick around across a restart.

[Vlatombe]

I've tried tweaking org.csanchez.jenkins.plugins.kubernetes.pipeline.RestartPipelineTest#taskListenerAfterRestart which uses RestartableJenkinsRule, checking nodeProperties after restart, but somehow the assertion already worked, which si weird, unless I'm missing something else in the workflow (outside of test setup) that would make this behave differently?