Rename glass.core.array to glass.arraytools

[paddyroddy]

Describe the Bug

Picked up by ruff==0.9.1 in #477. For now I have suppressed with # noqa: A005.

To Reproduce

import glass
...

Expected Behaviour

No response

Actual Behaviour

No response

Version In Use

2024.3.dev32+g0b41f16

Additional Context

- Python version:
- Operating system:

[ntessore]

Do we care?

[paddyroddy]

@ntessore it's an up-to-you situation. It could cause unwanted issues https://docs.astral.sh/ruff/rules/stdlib-module-shadowing, but if you want to keep it then please close this issue.

[ntessore]

I realise that it could cause issues in general, but I can vouch for the fact that we are not going to use the stdlib array module 😄

[ntessore]

That said, if we don't want to override the rule on a case-by-case basis, we can also rename that module to something else. I really don't care!

[Saransh-cpp]

This can definitely create problems. I'd suggest renaming the module to lib (numpy's broadcasting functions live in lib) or numeric (for trapezoidal rules). Other options would be to split the module into two modules, lib and numeric, or just keep all of it directly under the namespace of core (which sounds nice too - move all the functions to __init__.py_.

Let me know which one sounds good and I can create a PR!

[ntessore]

If glass.core.algorithm becomes glass.algorithm (#513) then we could remove glass.core entirely, and make this glass.arraytools or whatever you prefer?

[Saransh-cpp]

That makes sense. arraytools sounds much more better.