Add fractures_06.txt to cache data

[michaelgrund]

As suggested in #794 this PR adds the remote file fractures_06.txt to the cache workflow which is used to generate e.g. the gallery example for the upcoming rose wrapper. It's also heavily used for the testing of rose.

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 adding new functionality, add an example to docstrings or tutorials.

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]

I'm reopening the PR because the data file still needs to be cached before PR #1101.

[seisman]

The "Cache Data" workflow runs every Sunday. To cache the data before the next scheduled run, you need to uncomment the pull_request: line and commit the changes, wait for the CI run to finish, and comment the pull_request: line again.

See the commits history in RP #1085 for an example.

[michaelgrund]

The "Cache Data" workflow runs every Sunday. To cache the data before the next scheduled run, you need to uncomment the pull_request: line and commit the changes, wait for the CI run to finish, and comment the pull_request: line again.

See the commits history in RP #1085 for an example.

Thanks for guiding me @seisman 😉.

Edit: done