Comment out most of 430060e9.  Clean-up some dependencies in top-level Makefile

This reverts commit 430060e9.

That commit has some unexpected side-effects

Makefiles.*: It should be possible to run 'make menuconfig' with no .config and no Make.defs file.  This change removes the dependency on Make.defs, but does not solve the problem of the missing .config file.  Without a .config file, it is not currently possible for the Makefile.* to correctly setup up the symbolic links to directories.

In the menuconfig target, the context dependency was executed before kconfig-mconf.  That was necessary because the link at apps/platform/board needed to be set up before creating the apps/Kconfig file.  Otherwise, the platform Kconfig files would not be included.  But this introduces the chicken-and-egg problem in some configurations.

In particular:  (1) An NX graphics configuration is used that requires auto-generation of source files using cpp, (2) the configuration is set for Linux, but (3) we are running under Cygwin with (4) a Windows native toolchain.  In this case, POSIX-style symbolic links are set up but the Windows native toolchain cannot follow them.

The reason we are running 'make menuconfig' is to change from Linux to Cygwin, but the target fails.  During the context phase, NX runs CPP to generate source files but that fails because the Windows native toolchain cannot follow the links.  Checkmate.

This was fixed by changing all of the make menuconfig (and related) targets.  They no long depend on context being run.  Instead, they depend only on the dirlinks target.  The dirlinks target only sets up the directory links but does not try to run all of the context setup; the compiler is never invoked; no code is autogeneraed; and things work.

This change fixes a build problem that only occurs when reconfiguring from Linux to Windows or vice-versa.  It is a problem that was present but not usually experienced until two things happened:  (1) The pre_config target was added to run before the menconfig operation and (2) the context target was added before the pre_config target in order to set up the correct symbolic links (in the apps/platform directory) needed by the pre_config target.

But then now if you start with a Linux system and run 'make menuconfig' to switch to Linux, the context target will execute first and set up POSIX style symbolic links before doing the menuconfig.  Then after the menuconfig, the make will fail on Windows if you are using a Windows native toolchain because that native toolchain cannot follow the Cygwin-style symbolic links.

The first here is to also execute the clean_context AFTER executing menuconfig.  A lot more happens now:  It used to be that doing 'make menuconfig' only did the menuconfig operation.  No it does context, pre_config, menuconfig, clean_context.  Not nearly as snappy as it used to be.

Backout most of changes from 4d331ec09b2fc72636f86be628ea2f69381 and 8afe7216.  Does not work as expected.

Add configuration logic to include a Kconfig file in each custom configuration.  Includes adding a dummy custom board configuration directory.  A consequence of this that each custom board directory will now need to contain a Kconfig file.  NOTE also that the new board directory does not take effect in the configuration menues until the NEXT time you run 'make menuconfig'

Build system: Add 'make oldconfig' target.  Use this option in tools/testbuild.sh.  Add --silent option to tools/refresh.sh so that it can be run in batch without human interaction

Separate flat, protected, and kernel mode library selected into separate files.  The conditional logic as exceed my able to comprehend and maintain the selections.

Trick the top-level makefiles into building the SYSCALL proxy library but then not actually linking with it

Support for the older, manual configurations has been completely removed from the NuttX build system