Support for hidden config folders

[q-wertz]

Description

In my opinion it would be nice as maintainer of a package/template to also hand over some config folders and files to the users of my package.

In my case for example the configuration for vscode which is stored in a .vscode folder. Then the users could start directly writing in the template and do not have to think about which VSCode extensions they need to install and settings they have to adapt.
In my experience (only using a self-generated local package) the hidden folder in my template folder is not copied when I run typst init <@local>/<PROJECT>.

Some possibilities that come to my mind:

1. Add an optional parameter to typst init (e.g. --include-hidden or --include-optional) so that the user can decide if she/he really wants those folders
2. In the typst.toml add a configuration option that defines whether hidden files/folders should be included from in the template folder on initialization
   (Currently I cannot think of a usage scenario where a package maintainer would put something in the template folder that should not be included on typst init)
3. A combination of 1 and 2