sqlite: update README.chromium to reflect sqlite upgrade process changes

- Chromium doesn't need compat/ and fossil/.
- Use variable to avoid hardcoded version.
- The year is now 2019 (only used once so this should be ok).

Bug: 936694
Change-Id: If01ba58755bc692d6104f525cbc496ad628901d1
Reviewed-on: https://chromium-review.googlesource.com/c/1493263
Commit-Queue: Darwin Huang <huangdarwin@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#636593}

third_party/sqlite/README.chromium

@@ -155,18 +155,20 @@ export GNU_SED=sed  # OSX: "brew install gnu-sed", then use "gsed" here.
 #### Download and unpack the new SQLite release.
 git new-branch sqlite-new-upstream
 # URL from "Alternative Source Code Formats" at https://sqlite.org/download.html
-curl https://sqlite.org/2018/sqlite-src-${NEW}.zip > upstream.zip
+curl https://sqlite.org/2019/sqlite-src-${NEW}.zip > upstream.zip
 mkdir sqlite-src-${NEW}
 unzip ./upstream.zip -d sqlite-src-${NEW}
 rm ./upstream.zip
 mv sqlite-src-${NEW}/sqlite-*/* sqlite-src-${NEW}/
+rm -r sqlite-src-${NEW}/sqlite-*/.fossil-settings
 rmdir sqlite-src-${NEW}/sqlite-*/
+rm -r sqlite-src-${NEW}/compat
 xdg-open sqlite-src-${NEW}  # Make sure everything looks right.
 
 #### Add the new release code in a separate CL, for code review sanity.
 git add sqlite-src-${NEW}  # Committing the code as downloaded, on purpose.
 git clean -i -d -x sqlite-src-${NEW}  # Make sure no file is git-ignored.
-git commit -m "sqlite: Add code for release 3.28.0"
+git commit -m "sqlite: Add code for release ${NEW}"
 git cl upload  # Have the new code in a separate (impossible to review) CL.
 
 #### Create a branch for the old SQLite release's upstream version.