Move PrivetV3ContextGetter into separate file next to privet_v3_session

Move PrivetV3ContextGetter into separate file next to privet_v3_session

Code move only, no changes in logic.
PrivetV3ContextGetter is going to be used by gcd_private API

BUG=551631
Committed: https://crrev.com/ceae22bb94b76976800fa6d78f40e002cff9e35a
Cr-Commit-Position: refs/heads/master@{#359209}

[Vitaly Buka (NO REVIEWS), 2015-11-11 03:01:50]

Description was changed from

==========
Move PrivetV3ContextGetter into separate file next to privet_v3_session

PrivetV3ContextGetter is going to be used by gcd_private API

BUG=551631
==========

to

==========
Move PrivetV3ContextGetter into separate file next to privet_v3_session

PrivetV3ContextGetter is going to be used by gcd_private API

BUG=551631
==========

[Vitaly Buka (NO REVIEWS), 2015-11-11 03:01:51]

vitalybuka@chromium.org changed reviewers:
+ alekseys@chromium.org

[Vitaly Buka (NO REVIEWS), 2015-11-11 03:02:19]

vitalybuka@chromium.org changed reviewers:
+ davidben@chromium.org, mmenke@chromium.org

[Vitaly Buka (NO REVIEWS), 2015-11-11 03:02:58]

Description was changed from

==========
Move PrivetV3ContextGetter into separate file next to privet_v3_session

PrivetV3ContextGetter is going to be used by gcd_private API

BUG=551631
==========

to

==========
Move PrivetV3ContextGetter into separate file next to privet_v3_session

Code move only, no changes in logic.
PrivetV3ContextGetter is going to be used by gcd_private API

BUG=551631
==========

[Vitaly Buka (NO REVIEWS), 2015-11-11 03:03:08]

The CQ bit was checked by vitalybuka@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2015-11-11 03:04:25]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1435743004/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1435743004/1

[commit-bot: I haz the power, 2015-11-11 03:43:07]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-11-11 03:43:07]

Dry run: This issue passed the CQ dry run.

[Aleksey Shlyapnikov, 2015-11-12 00:08:45]

lgtm

[davidben, 2015-11-12 00:11:30]

(Did you want me to review this? I notice I'm a reviewer but didn't actually get
an email until just now. I don't think I have any particular OWNERS coverage or
familiarity with this code, so I'm not sure what I can contribute here.)

[Vitaly Buka (NO REVIEWS), 2015-11-12 00:53:22]

On 2015/11/12 00:11:30, davidben wrote:
> (Did you want me to review this? I notice I'm a reviewer but didn't actually
get
> an email until just now. I don't think I have any particular OWNERS coverage
or
> familiarity with this code, so I'm not sure what I can contribute here.)

Probably not. I need to do few small refactoring like this before I send Privet
Cert Verifier CL.
Final verifier and context will need review from you, Matt or Ryan.

All that staff will live in privet_v3_context_getter.* 
I am not sure if I can isolate security related stuff. It's likely each
incremental CL will 
have pieces of security and a lot of plumbing.

Maybe I can just ask to review only final results in privet_v3_context_getter.*
and
whatever you will find useful?

[Vitaly Buka (NO REVIEWS), 2015-11-12 00:53:29]

The CQ bit was checked by vitalybuka@chromium.org

[commit-bot: I haz the power, 2015-11-12 00:54:01]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1435743004/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1435743004/1

[commit-bot: I haz the power, 2015-11-12 02:34:14]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-11-12 20:02:48]

Patchset 1 (id:??) landed as
https://crrev.com/ceae22bb94b76976800fa6d78f40e002cff9e35a
Cr-Commit-Position: refs/heads/master@{#359209}