Remove InhomogeneousTupleVariable

[EmilyBourne]

Remove the InhomogeneousTupleVariable class. Fixes #1583 There is now enough information in the types to make this class unnecessary. Removing it allows inhomogeneous tuples to be used in classes (as it was previously not possible to combine DottedVariable and InhomogeneousTupleVariable).

Commit Summary

• Use the symbolic_alias category in a Scope to map an indexed element of an inhomogeneous tuple to the equivalent variable.
• Create _build_X functions for functions which accept inhomogeneous tuple arguments (created SemanticParser._build_PythonTupleFunction and SemanticParser._build_NumpyArray). This allows the variables to be collected from the scope during the building process
• Allow a PyccelUnarySub to be used as an index (to facilitate indexing with literals)
• Add a is_literal_integer function to determine if an expression is a literal integer
• Recognise inhomogeneous tuples via their class type
• Remove InhomogeneousTupleVariable
• Ensure IndexedElement can handle inhomogeneous tuple objects.
• Don't declare inhomogeneous tuples (their elements are now already present in the scope)
• Clarify use of dtype/class type in FCodePrinter._print_Declare
• Correct type annotation printing in Python (quotes are no longer present to be removed)
• Raise a warning if trying to wrap tuples
• Clean up tuple handling in _visit_Assign. Fixes COVERAGE : tuples in _visit_Assign Function #1392
• Extract printed inhomogenous tuple variables into PythonTuple at the semantic stage
• Increase coverage
• Add a test for inhomogeneous tuples in classes

[pyccel-bot]

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

Please begin by requesting your checklist using the command /bot checklist

[EmilyBourne]

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

[pyccel-bot]

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

[EmilyBourne]

/bot run pr_tests

[pyccel-bot]

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

[EmilyBourne]

/bot run spelling

[pyccel-bot]

It seems like you have forgotten to complete your checklist for this pull request. Please check the list here, fix the missing items and let me know when everything is ticked and fixed with /bot mark as ready.

[pyccel-bot]

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

[pyccel-bot]

Hey @pyccel/pyccel-dev ! @EmilyBourne has just created this great new pull request! Check it out and let me know what you think!

[Farouk-Echaref]

Looks good and the new docs are well written as well.

[pyccel-bot]

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

[pyccel-bot]

Hey @yguclu, @EmilyBourne, this PR is looking pretty good. @EmilyBourne and @Farouk-Echaref think it is ready to merge. Could you add your expertise to confirm that this follows all the coding conventions and fits in Pyccel's future plans? Thanks 😄