C to Python wrapper rewrite

[EmilyBourne]

The C-Python API wrapper is unnecessarily complicated. It is very hard to understand and this makes it extremely difficult to develop any new features (e.g. class wrapping, see phase 3 of #453).

This PR completely rewrites the wrapper following the example already set by the bind-C wrapper. An additional stage is added to the treatment which wraps the code. In turn the CWrapperPrinter is stripped back to only retain printing functionalites.

List of changes

• Create new c_to_python_wrapper module, which contains the class CToPythonWrapper
• Use CToPythonWrapper object in function create_shared_library of module python_wrapper
• Provide optional parameters to the clone method of FunctionDef
• Add new classes BindCArrayVariable and BindCVariable to AST of bind-C (i.e. Fortran-to-C) wrapper
• Add new classes PyFunctionDef, PyInterface and PyModule to AST of C-to-Python wrapper
• Fix bug in C functions free_array and free_pointer of Numpy extension
• Update Pyccel version to 1.9.0

[EmilyBourne]

/bot run linux

[pyccel-bot]

Hello again! Thank you for this new pull request 🤩.

Here is your checklist. Please tick items off when you have completed them or determined that they are not necessary for this pull request:

• Write a clear PR description
• Add tests to check your code works as expected
• Update documentation if necessary
• Update Changelog
• Ensure any relevant issues are linked
• Ensure new tests are passing

[EmilyBourne]

/bot run linux

[EmilyBourne]

/bot run linux

[EmilyBourne]

/bot run linux

[yguclu]

Good job! This is a very neat refactoring! I have minor comments as usual.

[pyccel-bot]

@EmilyBourne, @yguclu has a few questions/comments about your code. Can you go through and see if you agree with them. If not go ahead and explain why. Once you've adressed all the comments let me know with /bot mark as ready and we will see if we can get approval.

[EniddeallA]

/bot run linux docs

[pyccel-bot]

Good job ! Your PR is using all the code it added/changed.

[pyccel-bot]

@yguclu, @EmilyBourne has been working hard and thinks that they have now replied to or fixed all your comments. Could you take another look at the PR and see if you can approve now?

[yguclu]

@EmilyBourne We forgot to update the version in the CHANGELOG file. I will fix this in the next available PR.

[EmilyBourne]

@EmilyBourne We forgot to update the version in the CHANGELOG file. I will fix this in the next available PR.

Oops. Probably all the changelogs need updating so the changes appear in the correct version

[yguclu]

@EmilyBourne We forgot to update the version in the CHANGELOG file. I will fix this in the next available PR.

Oops. Probably all the changelogs need updating so the changes appear in the correct version

We will definitely have some conflicts. Anyway, does this CHANGELOG look good to you?

[EmilyBourne]

@EmilyBourne We forgot to update the version in the CHANGELOG file. I will fix this in the next available PR.

Oops. Probably all the changelogs need updating so the changes appear in the correct version

We will definitely have some conflicts. Anyway, does this CHANGELOG look good to you?

Looks good