We don't really need the two bulleted lists:
 * In context, the previous section should give hints about what this means.
 * If the context isn't clear enough, then the links provide more concrete description.

1.  The title for section `civicrm.settings.php; settings.php;
wp-config.php` is very long. Split the section -- a longer one
which discusses `civicrm.settings.php` in more depth, and a shorter
which discusses similar files briefly.

2.  Add a section for `civibuild.conf`.

This way MkDocs will be able to report errors for broken links

Done with:

perl -0777 -i -pe \
's@(?<!!)\[([^\]]*)\]\((?!https?://)(?!mailto:)(/(?:(?:(?:/(?![\)#]))|[^/)#])(?!.md))+)/?(#[^)]*)?\)@[$1]($2.md$3)@gm' \
`find . -name '*.md'`

Move them into the dedicated page on PhpStorm. Why? Tim has expressed
some concern about the potential difficulty (and slippery slope) of
starting to maintain IDE-specific docs. I like the PhpStorm page, but I
can see where he's coming from to a certain extent. As such, I think it
will be a good compromise if we can keep all the IDE-specific stuff as
consolidated as possible.

Migrated from the following two sources

https://github.com/civicrm/civicrm-buildkit/blob/d20229ac9f63aaf183687157a5e655c953b81f5e/doc/daily-coding.md#housekeeping
https://civicrm.stackexchange.com/questions/17717/how-do-i-upgrade-civicrm-on-a-local-site-that-i-installed-with-buildkit-civibuil/17721#17721

Not adding internal redirects because these pages are so new.

Based on discussion here:
https://github.com/civicrm/civicrm-dev-docs/pull/189