[CO-367] Fixing esk of addresses in mkSigner

[paweljakubas]

Description

This is one of the series of fixes that deals with making integration tests green.
The current one is the fix to esk address in mkSigner. Thanks to that at least one transaction is successfull

Linked issue

https://iohk.myjetbrains.com/youtrack/issue/CO-367

Type of change

• 🐞 Bug fix (non-breaking change which fixes an issue)
• 🛠 New feature (non-breaking change which adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)
• 🏭 Refactoring that does not change existing functionality but does improve things like code readability, structure etc
• 🔨 New or improved tests for existing code
• ⛑ git-flow chore (backport, hotfix, etc)

Developer checklist

• I have read the style guide document, and my code follows the code style of this project.
• If my code deals with exceptions, it follows the guidelines.
• I have updated any documentation accordingly, if needed. Documentation changes can be reflected in opening a PR on cardanodocs.com, amending the inline Haddock comments, any relevant README file or one of the document listed in the docs directory.
• CHANGELOG entry has been added and is linked to the correct PR on GitHub.

Testing checklist

• I have added tests to cover my changes.
• All new and existing tests passed.

QA Steps

Screenshots (if available)

[adinapoli-iohk]

LGTM, @paweljakubas . I have a minor note of style for the comment, but that can be addressed separately.

[adinapoli-iohk]

Minor typo, that's esk. I would omit the "esk address fix" part completely, We can just say "we need to use the ESK..." exactly as you are doing now.