Clean PythonCodePrinter and add dtype property

[EmilyBourne]

Remove the duplicate _print_NumpyArray function from PythonCodePrinter. The original _print_NumpyArray function is more accurate as it specifies the dtype etc explicitly.
Specifying the dtype explicitly makes issue #1377 reproducible. To fix this problem support is added for a.dtype expressions (Fixes #1421) using the similar function np.result_type. The initialisation dtype is saved and used in the Python printer. This is a work-around until #1334 is resolved well enough to define a clear issue. Additionally a warning is raised if the Python code is not consistent. Fixes #1377

Additional commits

• Simplify bot linux/windows/macosx output to reduce duplication. Change regex for C now that the test is no longer verbose.
• Stop generating numpy.bool in code as it has been deprecated by NumPy. Instead use the default bool (with precision -1).
• Add support for NumPy's short type names
• Reduce duplication in the Python printer
• Remove outdated skips on tests
• Stop array error tests failing in developer mode

[EmilyBourne]

This PR doesn't need to fix #1258 as it is fixed in #1280. The tests are migrated there. The tiny change remaining in this PR is preserved

[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

[pyccel-bot]

Unfortunately your PR is not passing the tests so it is not quite ready for review yet. Let me know when it is fixed with /bot mark as ready.

[EmilyBourne]

/bot run linux

[EmilyBourne]

/bot run docs

[EmilyBourne]

/bot run pr_tests

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

This looks good to me! I have a few comments and questions.

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

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