Surface KspOptions (or some of it's data) within SymbolProcessorEnvironment

[nak5ive]

From within a processor, it would be helpful to know some project-level information. ie: base directory, various output directories, etc. The CodeGenerator has access to a lot of this information (derived from KspOptions), but all of it is within private APIs.

Making this information available within the processor environment would enable more custom output, and potentially bring variant-awareness to the processor itself.

[kazemcodes]

Need this feature for #1850