[FEAT] Use more of upstream config.yaml

[RollingStar]

Is this a new feature request?

• I have searched the existing issues

Wanted change

There's a mismatch between the config here and the default beets config:

https://github.com/beetbox/beets/blob/master/beets/config_default.yaml

https://github.com/linuxserver/docker-beets/blob/master/root/defaults/config.yaml

Perhaps most critically is this part in upstream:

import:
write: yes
copy: yes
move: no

This means "copy all imported music to a new folder, and write new tags into the copied files, and leave the raw imported files alone", basically.

This repo has:
import:
write: yes
copy: no
move: yes

This is a source of confusion, with a popular YouTuber (Techno Dad Life) recommending a change from these defaults. https://youtu.be/IQGM52MiIqg?t=198

Is there a reason for this?

Reason for change

I can't find any commit where upstream has move:yes.

https://github.com/beetbox/beets/commits/master?after=cc7abe3a4734de73c86cb9ba6253c6a5596a042b+69&branch=master&path%5B%5D=beets&path%5B%5D=config_default.yaml&qualified_name=refs%2Fheads%2Fmaster

Proposed code change

No response

[github-actions]

Thanks for opening your first issue here! Be sure to follow the bug or feature issue templates!

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[RollingStar]

thanks

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[RollingStar]

cool

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions]

This issue is locked due to inactivity