Support routing PI extractor output to multiple spaces based on time series filters

Today, the PI extractor can only write time series instances to a single target space per deployment, even when the underlying PI server contains data for multiple sites or governance domains. The only practical workaround is to run many PI extractor instances against the same PI server, each with different tag filters and a different target space, which is hard to scale and operate. [Governance & spaces; Multi-space limitation]

I would like the PI extractor to support multiple target spaces from a single deployment, where the space is selected per time series based on configurable filters. Typical examples would be routing by tag name prefix or pattern (for example, ABU* to space site-abu, RUW* to space site-ruw), or by PI point attributes / metadata mapped to specific spaces. [Filter-based routing idea; Enterprise scaling concern]. This capability would avoid both the operational overhead of many parallel extractor instances.