Fix linting errors in go1.9.1

* Update gometalinter config

gometalinter now uses `maligned` instead of `aligncheck`
(https://github.com/alecthomas/gometalinter/pull/367), so we need to update our
config accordingly.

* Update gometalinter

* Disable gotype linter

gotype does not seem to play nicely with the gb vendor directory. In
particular, it wants each of our dependencies to be built and installed (see
https://github.com/golang/go/issues/10969), but (empirically) it will not
accept them being installed in `pkg` but insists on them being in `vendor/pkg`.

This presents a problem because `gb build` builds the packages into `pkg`
(which doesn't seem entirely unreasonable since `.` comes before `vendor` in
`$GOPATH`). `go install github.com/x/y` does install in `vendor/pkg` but
requires us to know the name of each package.

The general conclusion of https://github.com/alecthomas/gometalinter/issues/91
seems to have been that the easiest thing to do is to disable `gotype` for now.

* Fix `unparam` lint

* Fix goshadow lint

Signed-off-by: NAndrew (anoa) <anoa@openmailbox.org>

Take the keyring init from the client-api-server and the monolith out to a
shared file

Signed-off-by: NMichael Telatynski <7t3chguy@gmail.com>

* Federation: Implement Query Profile API

Implements the server portion of: `GET
/_matrix/federation/v1/query/profile?user_id=...&field=...`

Closes #278
Signed-off-by: NAndrew (anoa) <anoa@openmailbox.org>

* Properly export profile-related structs and fix wording
Signed-off-by: NAndrew (anoa) <anoa@openmailbox.org>

* Check provided user's domain matches our own.

This has two benefits:

1. Using channels makes it easier to time out while waiting
2. Allows us to clean up goroutines that were waiting if we timeout the
   request

This is in preperation for implementing various federation APIs that
need to build events.

This seems to have been missed when we folded all the readers and
writers packages into routing.

Signed-off-by: NPaul Tötterman <paul.totterman@iki.fi>

Including:
- Handle timeout=0 correctly
- Always return immediately on initial sync
- Handle spurious wake ups from the notifier

The way we store the partition offsets for kafka streams means that when
we start after a crash we may get the last message we processed again.
This means that we have to be careful to ensure that the processing
handles consecutive duplicates correctly.

Signed-off-by: NRemi Reuvekamp <git@remireuvekamp.nl>

The HTTP handlers in the components are split into reader and writer directories. This was a fairly arbitrary distinction, and turns out to not be so helpful. Most read APIs have a corresponding write API, and it is more natural for them to be in the same file rather than in different directories.

The prior naming was confusing, OutputRoomEvent consumed
OutputNewRoomEvents

* Implement filter POSTing and GETting.
Signed-off-by: NJan Christian Grünhage <jan.christian@gruenhage.xyz>

* Add missing '}' typo introduced during merge

* Still trying to fix that merge...

* Fix linting

Signed-off-by: NMTRNord <mtrnord1@gmail.com>

* Implement GET /rooms/{roomID}/state/{type}/{stateKey}

* Add comments

* Add config for setting up a jaeger opentracing reporter

* Remove redundant comment

* Add opentracing Spans to the HTTP APIs

* Add opentracing spans to the HTTP RPC clients

* Set the span in the request context

* More docstring

* Implement setting alias during room create

* Implement shared secret registration

* Use HexString from gomatrixserverlib

* Correctly check username validility

* Move prev event structure to component-wide types

* Renamed key for better understandability

* Implement /state endpoint

* Change rowsToEvents() to return an empty slice instead of nil in case of empty result set

* Doc

* Fix forgotten comma

* Specify HTTP method

* Update comment

* Remove debug fmt.Println