Ignore some paths from file watcher

[kshepherd]

Watching all these directories can cause systems to exceed maximum watched files / inotify limits, especially in dev mode with IDEs etc also watching files.

I've included node_modules, and some basic vcs and project dirs that should be excluded.

  watchOptions: {
    // Ignore directories that should not be watched for recompiling angular
    ignored: [
      '**/node_modules', '**/_build', '**/.git', '**/docker',
      '**/.angular', '**/.idea', '**/.vscode', '**/.history', '**/.vsix'
    ]
  },

Testing

It's actually not super trivial to 'see' watched files, but if you can reproduce the underlying issue (get your system into a state where inotify limit is exceeded), then you can run with and without this change, and review any errors listed, to see whether the file watcher is attempting to watch e.g. node_modules

(if anyone has any better test procedures please let me know!)

Notes

Documentation: https://webpack.js.org/configuration/watch/#watchoptions

Note, there is also a way to do this in tsconfig.json but in my practical testing it wasn't taking effect (see: https://www.typescriptlang.org/tsconfig/#watchOptions)

Checklist

This checklist provides a reminder of what we are going to look for when reviewing your PR. You do not need to complete this checklist prior creating your PR (draft PRs are always welcome).
However, reviewers may request that you complete any actions in this list if you have not done so. If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!

• My PR is created against the main branch of code (unless it is a backport or is fixing an issue specific to an older branch).
• My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
• My PR passes ESLint validation using yarn lint
• My PR includes details on how to test it. I've provided clear instructions to reviewers on how to successfully test this fix or feature.
• If my PR includes new features or configurations, I've provided basic technical documentation in the PR itself.

[tdonohue]

Seems harmless to me, but I'd love to have a quick review from either @artlowel or @atarix83 .

The list of directories makes sense to me though! Thanks @kshepherd !

[artlowel]

Thanks @kshepherd!

That makes sense

[dspace-bot]

Successfully created backport PR for dspace-7_x:

• [Port dspace-7_x] Ignore some paths from file watcher #3297

[dspace-bot]

Successfully created backport PR for dspace-8_x:

• [Port dspace-8_x] Ignore some paths from file watcher #3298