Variable type annotations for homogeneous tuples

[EmilyBourne]

Handle the indexing of a tuple class for type annotations. For now only homogeneous tuples are handled. Inhomogeneous tuples will be simple to add once InhomogeneousTupleVariable is deprecated.
Fix handling of homogeneity in PythonTuple. Fixes #1182

Commit Summary

• Fix handling of homogeneity in PythonTuple
• Correct class type in PythonMin and PythonMax
• Update documentation to describe tuple annotations
• Add LiteralEllipsis class to help describe homogeneous tuple type annotations
• Handle slices passed to NumpyArray
• Add class type checking to type change checks
• Allow _visit_X functions to be added for built-in classes.
• Add tests
• Fix test containing a type change (list to ndarray)
• Use pyccel_to_sympy to allow the use of a*(3-1) syntax where a is a tuple. Previously this was precluded as 3-1 is not an integer
• Remove dead code

[pyccel-bot]

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

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

[EmilyBourne]

/bot run linux

[EmilyBourne]

/bot run pylint pyccel_lint docs spelling

[EmilyBourne]

/bot run pylint docs

[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

[EmilyBourne]

/bot run coverage pylint pyccel_lint docs spelling

[pyccel-bot]

There seems to be lines in this PR which aren't tested. Please take a look at my comments and add tests which cover the new code.

If this is modified code which cannot be easily tested in this PR please open an issue to request that this code be either removed or tested. Once you have done that please leave a message on the relevant conversation beginning with the line /bot accept and referencing the issue.

Similarly if the new code cannot be tested for some reason, please leave a comment beginning with the line /bot accept on the relevant conversation explaining why the code can't be tested.

[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]

Everything looks good to me; the code changes seem understandable, and the documentation is clear.

[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 😄

[yguclu]

/bot run pr_tests

[pyccel-bot]

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