Use Arc<Store> instead of Store for lazy loading

[ghost]

Description

Change store's type used in Router and Extract to wrapped one, to load configurations after extraction.
This change affects to public trait.

Motivation and Context

Sometimes we define services for SoC. They would be dependent on another services.
Tide has per-endpoint configuration, so every services should be able to read it.

One way for it is passing a store's reference in services' constructor recursively while extraction. This looks good, but if some services depend on same services, duplicate object will be created.
Another way is extract (partial) clone of store and share it across services. If the store is big, per-request clone will be high cost.

This change helps latter one. Instead of cloning a store directly, we can clone just shared reference with few overhead.

How Has This Been Tested?

There are no additional tests.
Implementations of Extract are affected, but it can be easily fixed.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[mmrath]

Why would services depend on Store? I would expect services to be independent of any of the types in tide.
Would you have some example code showing the benefit/usage?

[ghost]

@mmrath Sorry, actualy I have no Idea.
At the first I thought is to inject slog logger and configure logging strategies by per-endpoint, per-service, but I can not determine whether this use case is appropriate because of lack of experiences.

[aturon]

Closing this one, since the relevant concepts were removed in #156.