Improve optimistic update of datasetInfo

[JosephMarinier]

Description:

Improve optimistic update of datasetInfo. For example, if you update the project name in the config page (not yet possible), it will update instantly in the top navigation bar.

Checklist:

You should check all boxes before the PR is ready. If a box does not apply, check it to acknowledge it.

• ISSUE NUMBER. You linked the issue number (Ex: Resolve #XXX).
• PRE-COMMIT. You ran pre-commit on all commits, or else, you
  ran pre-commit run --all-files at the end.
• USER CHANGES. The changes are added to CHANGELOG.md and the documentation, if they impact
  our users.
• DEV CHANGES.
  • Update the documentation if this PR changes how to develop/launch on the app.
  • Update the README files and our wiki for any big design decisions, if relevant.
  • Add unit tests, docstrings, typing and comments for complex sections.

[christyler3030]

Is this the only validation needed? For example do you permit empty string as a value?

[JosephMarinier]

I say we let the back end do the validation, so we don't duplicate the logic. In this case, I think it does allow for an empty string, yes.
This is not really validation, but rather "is it present in the partial config?". I would like to put "name" in partialConfig, but even though name: string is required in AzimuthConfig, in Partial<AzimuthConfig> it becomes name?: string | undefined, so I must deal with the undefined (even though it can't happen in our code).
Does that make sense?