Put in a hack to allow images to go wider than 256 columns. If we see the x value go to 0 right after it's 255 and the image code and row number stay the same, treat it as a continuation. Issue 6335.

Rebuild touch bar when color presets change. It was not picking up changes on macOS 10.13. Mentioned in a comment in issue 5281

[Focuse follows mouse] If the mouse has not moved between when the app resigned active and when the app becomes active again do not make the window under the cursor key.

Set find bar text field's apppearance to light when there's a dark theme so it is legible. Issue 6330

Make reset (both user initiated and ANSI RIS) show the primary buffer when in alternate screen mode. Issue 6325

Update solarized light and dark color presets to match the SRGB colors from the spec. Issue 3989.

[tmux integration] Store "none" for the tab color when tab color is off for a session. This fixes a bug where new tmux sessions didn't use the profile's color. Uninitialized (which is now indicated as an unset tab color) should (and now does) mean to use the profile's value. "none" means no color. Otherwise it'll be a #hex value.

Issue 6320

Tiny typo fix

Draw tab color in white if the window appearance is dark. This happens to work for the main menu (it has a window!) as well as the context menu on a tab. Issue 6286.

This fixes the solarized dark background being slightly darker in iterm.
I also ran the same script to generate the colors for solarized light,
although I didn't check before if the colors were incorrect.

This changes solarized colors to use sRGB. The colors are calculated by
dividing the reference RGB values by 255.0 in ruby.

As discussed here: https://gitlab.com/gnachman/iterm2/issues/3989#note_47289852

These are the reference colors used:
```
SOLARIZED HEX     16/8 TERMCOL  XTERM/HEX   L*A*B      RGB         HSB
--------- ------- ---- -------  ----------- ---------- ----------- -----------
base03    #002b36  8/4 brblack  234 #1c1c1c 15 -12 -12   0  43  54 193 100  21
base02    #073642  0/4 black    235 #262626 20 -12 -12   7  54  66 192  90  26
base01    #586e75 10/7 brgreen  240 #585858 45 -07 -07  88 110 117 194  25  46
base00    #657b83 11/7 bryellow 241 #626262 50 -07 -07 101 123 131 195  23  51
base0     #839496 12/6 brblue   244 #808080 60 -06 -03 131 148 150 186  13  59
base1     #93a1a1 14/4 brcyan   245 #8a8a8a 65 -05 -02 147 161 161 180   9  63
base2     #eee8d5  7/7 white    254 #e4e4e4 92 -00  10 238 232 213  44  11  93
base3     #fdf6e3 15/7 brwhite  230 #ffffd7 97  00  10 253 246 227  44  10  99
yellow    #b58900  3/3 yellow   136 #af8700 60  10  65 181 137   0  45 100  71
orange    #cb4b16  9/3 brred    166 #d75f00 50  50  55 203  75  22  18  89  80
red       #dc322f  1/1 red      160 #d70000 50  65  45 220  50  47   1  79  86
magenta   #d33682  5/5 magenta  125 #af005f 50  65 -05 211  54 130 331  74  83
violet    #6c71c4 13/5 brmagenta 61 #5f5faf 50  15 -45 108 113 196 237  45  77
blue      #268bd2  4/4 blue      33 #0087ff 55 -10 -45  38 139 210 205  82  82
cyan      #2aa198  6/6 cyan      37 #00afaf 60 -35 -05  42 161 152 175  74  63
green     #859900  2/2 green     64 #5f8700 60 -20  65 133 153   0  68 100  60
```

Don't crash when you delete a password manager entry that is your only one and you are editing the password

Remove mechanism for catching proc_pidinfo and statfs timeouts. It was causing crashes, but I don't understand why. Perhaps mixing ARC and non-ARC code has some problem? I saw lots of crashes on 3.1.4 where proc_pidinfo exceeded the timeout and when it finally returned there was heap corruption. It looked as though the dispatch group had been freed even though there was an outstanding reference to it. At any rate, if proc_pidinfo is hanging you're going to have a bad time even without this workaround.

Avoid looking up a negative index when you have a tail find going (i.e., the find panel is open) and you clear the buffer and it becomes empty (i.e., there's nothing before the cursor such as a prompt at the time you do cmd-k). Issue 6271

Remove incorrect tooltip on "show mark" button in prefs.

Having merged in the PR for selecting an account after opening the password manager from a trigger, add manual retain-release code and rename ivar.