Set CCSID of deployed files to 1208 if needed

[sebjulliand]

Changes

Resolves #1995

On systems <= 7.3, the deployed files are created with a CCSID 819 (or at least different from 1208).
This PR checks (once per connection, during the first deployment - the check result is cached) if the CCSID needs to be set to 1208 after a successful deployment and runs the setccsid command if needed.

How to test this PR

Here is a query to list files with CCSID != 1208:

select path_name, ccsid
from table(qsys2.ifs_object_statistics( 
           start_path_name => '/deployment/path',
           subtree_directories => 'yes'))
where ccsid != 1208

This should be tested on two systems:

• On a system where stream files are created with CCSID 819 (IBM i OS <= 7.3)

1. Deploy the local workspace
2. Check the progress says Fixing files CCSID...
3. If running an action, check the following log appear in the task log: Deployed files' CCSID set to 1208
4. The SQL query above should not return any result

• On a system where stream files are created with CCSID 1208

1. Deploy the local workspace
2. Nothing should be logged about fixing the CCSID
3. The SQL query above should not return any result

Checklist

• have tested my change

[edmundreinhardt]

I have tested and this works!

[edmundreinhardt]

Is there a reason why this is targetting 2.11 instead of 2.10?

[worksofliam]

@edmundreinhardt 2.10.0 is basically finalized and we only need to do doc changes now.

[edmundreinhardt]

Just a shame because this is important to supporting IFS deployment. We were hitting this quite a bit on our test IBM i machines. For Code for i to support local development on 7.3 for example, this is critical. It is a small PR and should hopefully not be a big risk.

[worksofliam]

@edmundreinhardt I am going to test it today 😄

[worksofliam]

Tested on three systems and it works as expected. Good work @sebjulliand!