Examples: Replace deprecated "np.random.seed()" with "np.random.Generator()" (NPY002 warning by ruff)

[yvonnefroehlich]

Description of proposed changes

This PR aims to update the examples to follow ruff's NumPy rules, especially it addresses the NPY002 warning (please see https://docs.astral.sh/ruff/rules/numpy-legacy-random/):

NPY002 Replace legacy `np.random.seed` call with `np.random.Generator`

Example:

import numpy as np
np.random.seed(42)
np.random.normal()

is replaced by

rng = np.random.default_rng(seed=42)
rng.normal()

Affected examples:

• gallery: histogram - old -> new
• gallery: scatter_and_histograms - old -> new
• gallery: points - old -> new
• gallery: scatter - old -> new
• tutorial: cartesian_histograms - old -> new

Please note that the plots are not completely identical. This is because the generated random numbers are not identical.

Related to the PRs

• Tests: Replace deprecated "np.random.seed()" with "np.random.Generator()" (NPY002 warning by ruff) #2787
• Enable ruff's NumPy-specific rules #2782

Fixes #2779 partly

Reminders

• Run make format and make check to make sure the code follows the style guide.
• Add tests for new features or tests that would have caught the bug that you're fixing.
• Add new public functions/methods/classes to doc/api/index.rst.
• Write detailed docstrings for all functions/methods.
• If wrapping a new module, open a 'Wrap new GMT module' issue and submit reasonably-sized PRs.
• If adding new functionality, add an example to docstrings or tutorials.
• Use underscores (not hyphens) in names of Python files and directories.

Slash Commands

You can write slash commands (/command) in the first line of a comment to perform
specific operations. Supported slash commands are:

• /format: automatically format and lint the code
• /test-gmt-dev: run full tests on the latest GMT development version

[seisman]

The PR title makes no sense to people who don't know NPY002. Could you please update the PR title to make it more clear what the changes are?

[weiji14]

Minor suggestion to use kwargs, otherwise looks good! Just wait for the docs to be rebuilt and double-check that the transparency issue has been fixed with #2783.

[yvonnefroehlich]

The PR title makes no sense to people who don't know NPY002. Could you please update the PR title to make it more clear what the changes are?

I have improved the title, added the links to the previews, and expanded the comment explaining this PR.