Enable taxonomy, node type, and path matching for the default domain

The "Force default domain" option is harmful in many cases. But the alternative - leaving it off - severely limits multidomain functionality. What we need instead is to enable configuration of the default domain like other domains.

In configuring the module, users can select "Force default domain". Doing so means that all URLs not claimed by one of the non-default domains will be rewritten for the default domain.

This leads to significant issues however. One is AJAX. Default browser security settings usually block AJAX requests to other than the 'originating server'. E.g., if a site has the five star voting widget enabled and votable content displayed on several non-default domains, the AJAX fails because the AJAX callback path is forced to the default domain.

[I had other issues with "Force default domain" which caused me to switch it off, but I can't recall them exactly. I'll add details if they come back to me.]

If we simply switch off "Force default domain", however, we're left with no way to assign content or paths to the default domain. On a non-default domain, all paths stay on that domain except ones that point to another non-default domain.

What we should do is:

• Remove the "force default domain" option.
• For the default domain, add a configuration screen like those for the other domains, except without the various settings for site name, default theme, etc. (this is handled through the regular interface for the default domain).

That way we'll have the ability to assign content and paths to the default domain, without the problems of "Force default domain".