Ineffectual assignment of the envVars for connection pooler

[dmvolod]

Ineffectual assignment of the envVars for connection pooler if spec.TLS is specified.
@FxKu please have a look at this bug and try to fit it into the 1.9 if possible
Test case can be added, but this case should be covered by the linter

[FxKu]

unrelated change. What is it for?

[dmvolod]

This is fix when GOPATH installed explicitly (for example in GoLand IDE and multiple golang version installed, but not happens for the single and system golang version) code generation will be targeted to the GOPATH\src instead of the root project path.

[FxKu]

Thanks for raising @dmvolod. We wanted to add a unit test today and would have stumbled over it, I guess 😃
@jeremie-seguin fyi

[dmvolod]

We wanted to add a unit test today and would have stumbled over it

Seems to TestConnectionPoolerPodSpec need to be refactoring a bit and not ready for easy env vars validation. Probably it can be postponed to next release, as current situation can be handled by the linting step in the future, but complex test solution for env vars need much more time.
@FxKu wdyt about it?

[FxKu]

👍

[jopadi]

👍

[FxKu]

Thanks @dmvolod. Yeah we also noticed that pooler unit test need more work than what @jopadi and me expected.