Feature - Move from alpine to debian image

[ddelpiano]

Closes #CH-95

Implemented solution:

• replaced the alpine with the debian base image in cloudharness-base image
• replace the occurrences of cloudharness-base-debian with cloudharness-base and apk to apt where found
• created a configuration script for the migration, if the keyword is found in a file then it iterates the old words and ask the user if they want to replace them with the new, a python script runs the migration as well.
• integrated the above with harness_deployment and 2 new flags (one for migration, one for migration without input from the user)

How to test this PR:

• manually create an application in the applications folder and make this use the CLOUDHARNESS_BASE_DEBIAN image to create the application container, and also apk to install some packages

• run the harness_deployment tool with the migration flag

• check the files wiht the keyword created at the first step

• automated testing has been implemented as well to test the utils created and the perform_migration function.

Sanity checks:

• The pull request is explicitly linked to the relevant issue(s)
• The issue is well described: clearly states the problem and the general proposed solution(s)
• From the issue and the current PR it is explicitly stated how to test the current change
• The labels in the issue set the scope and the type of issue (bug, feature, etc.)
• All the automated test checks are passing
• All the linked issues are included in one milestone
• All the linked issues are in the Review/QA column of the board
• All the linked issues are assigned

Breaking changes (select one):

• The present changes do not change the preexisting api in any way
• This PR and the issue are tagged as a breaking-change

Possible deployment updates issues (select one):

• There is no reason why deployments based on CloudHarness may break after the current update
• This PR and the issue are tagged as alert:deployment

Test coverage (select one):

• Tests for the relevant cases are included in this pr
• The changes included in this pr are out of the current test coverage scope

Documentation (select one):

• The documentation has been updated to match the current changes
• The changes included in this PR are out of the current documentation scope

Nice to have (if relevant):

• Screenshots of the changes
• Explanatory video/animated gif

[ddelpiano]

@filippomc the changes requested are done. Thx