Implement default file path pattern for tables component

[savente93]

Issue addressed

Fixes #864

Explanation

In today's refinement we decided that components should take some variation of default_filename at init, and store that so it can be used for reading and writing unless the user overrides it by passing in an argument of their own.

In addition we did not explicitly discuss today, but it seems we have reached a consensus that:

• components that can contain multiple objects (e.g. they store a dictionary of something) should be names in plural form
• We do not want to expose constants for our default paths.

This PR brings TablesComponent up to date with that convention. I don't think any of the changelogs or documentation has to be updated for this, but feel free to let me know if you disagree.

Checklist

• Updated tests or added new tests
• Branch is up to date with v1
• Tests & pre-commit hooks pass
• Updated documentation if needed
• Updated changelog.rst if needed
• For predefined catalogs: update the catalog version in the file itself, the references in data/predefined_catalogs.yml, and the changelog in data/changelog.rst

Additional Notes (optional)

Add any additional notes or information that may be helpful.

[hboisgon]

Thanks for the update! GridComponent should be also be updated by can be done in another PR. Before merging do we use default_filename or filename as the argument of the init function? I don't mind but then ConfigComponent should be updated.
In a way filename also sounds good and avoids for the user to give the filename in read and write all the time from config so default_filename makes sense for plugins developpers but not necessarily for users:

global:
  components:
    config:
      type: ConfigComponent
      filename: model_config.toml
    grid:
      type: GridComponent
      filename: grid.nc
steps:
  - config.create
  - grid.add_data_from_rasterdataset
  - write