add(build-109): Add branched manifest for v109.0.0

Change-Id: Id2af3ba3c8c70402c1e12ae796f476cf25519f1c
churn(default): Rename full.xml to master.xml

I am going to start including the current branch manifest in master
instead of branching first to make the release workflow more normal:

- Update version info, commit
- Tag commit
- (later) Cut release branch at tag iff it needs to diverge from master

This will mean the version of master actually reflects the current
version number used in releases since master gets its version updated
first. The backwards scheme, which sorta made sense from a build
perspective, doesn't make sense from a SDK user's perspective.

Change-Id: I6dec04eeec2114ae05d4401fd1d5d5f8df280a85
Merge branch 'build-109' of ssh://github.com/coreos/manifest into default

Conflicts:
	default.xml

Change-Id: I39296b43fd4453d95abc14937813de1732bbb04c
bump(version): Update SDK version to 109

Change-Id: Id4a0c8bb8a40ebd9f19d8b78f80b47b909e0446b
Merge pull request #27 from marineam/release-reorg

Release reorg