Clean up GCC source locations #8
Description
The resolver uses a number of properties in package.json to locate source files for the build. Currently it uses:
build.gcc.gcc-src: Adds an array of source paths to the build.build.gcc.gcc-src-overrides: This replaces the above paths for a specific package. For example, a plugin could replace the source paths for its application.directories.srcanddirectories.lib: The default paths to check if neither of the above are specified.build.gcc.js: Additional paths to add.
The first three items are managed by the GCC src plugin, while the last one is added by the options plugin. To keep the configuration more in line with what it's being used for, I would suggest removing the first three items in favor of build.gcc.js.
Both gcc-src and directories can be easily replaced, but the overrides will require additional work. That property should be replaced with a mechanism to override any property for another package. It doesn't appear source overrides are currently used by any known projects so we could remove that support for now.