Add a tutorial for working with table inputs in PyGMT

[seisman]

Description of proposed changes

Explain the table input types as mentioned in #1268.

Preview: https://pygmt-dev--2722.org.readthedocs.build/en/2722/get_started/04_table_inputs.html
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

[yvonnefroehlich]

Just made some typo and formating comments. Have to look at the conent in more detail later.

[weiji14]

I/O means Input/Output, but this tutorial is only on inputs 🙂 Will the 'Output' part be added as a separate page? Or do we want multiple parts like:

• 4.1 PyGMT I/O: Table inputs
• 4.2 PyGMT I/O: Table outputs
• 4.3 PyGMT I/O: Grid inputs
• 4.4 PyGMT I/O: Grid outputs

[seisman]

Yes, that's my plan, but I may prefer to the following order:

4.1 PyGMT I/O: Table inputs
4.2 PyGMT I/O: Grid inputs
4.3 PyGMT I/O: Table outputs
4.4 PyGMT I/O: Grid outputs

[weiji14]

Thanks @seisman! Might need to update this once we get more PyArrow support (#2800), but good to start with the basics first!