Checkpoint to make sure config file is set up correctly added to the getting started guide

[miertla]

Description

Added a quick checkpoint to ensure the config file is set up correctly prior to users importing their music library. This was something I discovered later after running into an issue with my config file and hope it helps new users avoid the issues I had.

To Do

• Documentation. (If you've add a new command-line flag, for example, find the appropriate page under docs/ to describe it.)
• Changelog. (Add an entry to docs/changelog.rst near the top of the document.)
• Tests. (Encouraged but not strictly required.)

[sampsyo]

It's not a bad idea to have something like this! I have a suggestion for keeping this short and to the point; let me know what you think.

[sampsyo]

How about this slightly simplified version?

To check that you've set up your configuration how you want it, you can type
``beet version`` to see a list of enabled plugins or ``beet config`` to get a
complete listing of your current configuration.

[JOJ0]

@miertla what do you think of sampsyo's suggestion? If you like it, do you have a minute to update your pull request. I would press the merge button then :-) Thanks!

[JOJ0]

@miertla?

[JOJ0]

Suggested change

	To check that your config file is set up correctly run ``beet version``. This should return your
	beets version, Python version, and a list of installed plugins. If no plugins are displayed, but
	there are plugins listed in your config file go back to the steps above to set up the config
	file properly before importing your music library. You can also run ``beet config`` which will
	display more in-depth details about each enabled plugin.
	To check that you've set up your configuration how you want it, you can type
	``beet version`` to see a list of enabled plugins or ``beet config`` to get a
	complete listing of your current configuration.

Adding @sampsyo's idea as a suggestion