Core: save session as soon as a the sequence is incremented

Just be safe, let's not wait until other part of the code saves the
session, and let's do it right here on the spot, where we know it
changes.

@Laituex was having a ErrCode=32 'msg_seqno too low' problem and this
is the second thing we suspected to be the culprit, because if there's
any issue (e.g. exception) that makes the session not be saved after
the sequence got incremented, then an old sequence would be used the
next time upon loading an old session file.

(Backported from sochix@1b06473)

Core: don't consider MediaOnly DCs at reconnect

Fixes sochix#935

(This commit was brought from TLSharp [1] version 0.1.0.554.)

[1] sochix@9a6e391

nugetUpload: honor git tags as versions