Workspace anchors should ignore .next folder by default

[TobyDS]

Describe the bug
Next.JS creates a .next folder. I believe this is done by the create-next-app cli tool but could be wrong. This should be ignored by default, as it is auto generated, slows down the extension, and returns TODOs not relevant the user.

To Reproduce
Steps to reproduce the behavior:

1. Create a next.js app/open project containing next.js
2. Run the workplace anchors scan in the extensions menu
3. Observe the long time needed to scan and irrelevant TODOs

Expected behavior
The TODOs form within the .next folder should have been excluded from the scan by default

Proposed Solution
This issue can be solved by adding .next to the default configuration for commentAnchors.workspace.excludeFiles. The new glob pattern as would be as follows:

"commentAnchors.workspace.excludeFiles": "**/{node_modules,.git,.idea,.next,target,out,build,bin,obj,dist,vendor}/**/*"