Tweak aurelia package reexports

[ekzobrain]

Tweak aurelia package reexports

[bigopon]

Im not entirely sure about why. I think the motivation was to have it all in one and we will just encourage devs to import from the aurelia for simplicity. Maybe it shouldnt be this way, some times it feels weird to me.
Cc @brandonseydel @Vheissu @3cp @Sayan751 @jwx

[ekzobrain]

Fetch client docs (https://docs.aurelia.io/aurelia-packages/overview/setting-up) examples import from '@aurelia/fetch-client'.

Currently fetch-client is the only package that is positioned as a plugin, but required and reexported by aurelia. Why not dialog / validation / etc then?

[bigopon]

Fetch client being far more used than the rest is the reason I believe.

[ekzobrain]

Router is definitely used not less, but it is not reexported...

[bigopon]

It used to be reexported as well, but we removed it. Maybe let's cleanup the fetch plugin and let aurelia just be the core modules.

[Sayan751]

We can remove the reexports from the plugins. I see no conflict with that.

[Vheissu]

I think removing the exports is fine. I will admit our exports situation is weird anyways. For example, the watch decorator isnt in the main Aurelia package as an export, so you have to get it from runtime/html.

[ekzobrain]

I think removing the exports is fine. I will admit our exports situation is weird anyways. For example, the watch decorator isnt in the main Aurelia package as an export, so you have to get it from runtime/html.

watch is there already

[bigopon]

Resolved by #1926