Fix infinite loop in bitmap_drv_init_mode() if scaling results in
larger than max size.

This uncovered an issue in resize_window() which would cause the
screen to be corrupted due to vstat not agreeing to the actual window.

This was ending up using an uninitialized value

It appears its matching based on the class, not the application.
Since this was hard-coded to CIOLIB based on the idea of using
resources to customize all CIOLIB windows, this didn't match the
SyncTERM .desktop file, so ChromeOS assumed it was "something else"

Add yet another ciolib_initial_* variable to set this, and she's
finally good!

Implied by _NET_WM_PID being set, so may as well do it.

Seems like a good idea, should allow WMs to kill hung processes and
stuff like that.

The XSynchronize disablement is the most important here... didn't
realize it defaulted to enabled, which has been slowing down a *lot*
of stuff for a long time... not that there's much left that benefits
from disabling Synchronized XLib except this new terrible icon thing.

This allows X11 stuff to work properly.

Actually install the colormap we create.
Remove the 48x48 icon.

As it happens, ChromeOS completely ignores the X11 icons and instead
does some weird magic to drag the icon .png file out of the VM and
uses that.  Basically, getting the icon to work appears to mean
putting some properly named files into magic directores.

USize was wrong, PSize wasn't set, and PBaseSize was set, but flag wasn't.

Also, set both _NET_WM_ICON and WMHint icon pixmap

It seems whatever WM XWayland uses doesn't actually use _NET_WM_ICON
like pretty much everything else for the last 30 years does, so we
need to go old-school or settle for the default pengion icon, which
offends me personally.

The bracketpaste "bit" was set to 0x16, not 0x10 or 16 as intended.
Erase line would erase the wrong line if the scrolling region didn't
start on line 1.

The sketchiest bit here is removing the uifc -> conio dependency
which, since it needs to depend on conio_sdl now means if something
is relying on that, it will need an explicity dependency...

We'll see what the pipeline says.

"I can't think of a reason I'd want scfg and echocfg to remain windows (gui) programs"
                                              -- Digital Man

While I'm here, hack up some SyncTERM vcxproj stuff (which almost
certainly doesn't work, but since I can actually test it now, I
may as well try)

At the same time, add BD, BE, PE, and PS to the terminfo entry.

Note that it seems this is "normally" detected by seeing if $TERM
contains "xterm" which shouldn't work with SyncTERM (which is wildly
incompatible), but the terminfo source file here:
https://invisible-island.net/ncurses/terminfo.ti.html
Gives us hope in the form of this comment:

https://invisible-island.net/xterm/xterm-paste64.html

Bracketed paste was introduced by xterm patch #203 in May 2005, as part of a
larger feature for manipulating the clipboard selection.  Few terminals aside
from xterm fully implement the clipboard feature, but several copy this
detail.  The names for the extended capabilities here were introduced by vim
in January 2017, but used internally.  In 2023, vim patch 9.0.1117 is needed
to work with this change.

That is to say that it likely won't work on anyone's system today
(except maybe Cyan's), but it may magically start working in the
future... assuming tic supports these capnames.  No real clue there
since there's absolutely no termcap support, and I use FreeBSD.

Previously, delete lines would erase the line above the current one.
This was visible in vim which makes extensive use of delete line
to scroll.

In theory, this will allow higher quality scaling in GDI mode if
the graphics driver supports it...

It doesn't look like the drive used for VirtualBox does though, so
I can't tell if it does anything or not.

Use the default visual and depth instead of "best"
Use Xrender for sclaing when library is available and server supports it
Set VisualIsRGB8 when possible

This should prevent programs using rgbmap (ie: SyncTERM) from
having an exectuable stack on Linux.

- getscaling() incorrectly used an int intermediate variable
  This would force scaling to an integer value when read.
- Only parse ConfigureNotify events describing a change to the SyncTERM window
  It appears that XWayland on ChromeOS was occasionally sending a
  ConfigureNotify event describing some other window to SyncTERM,
  and that window had a 1x1 size, which would cause SyncTERM to
  assert minimum size again (usually 640x480), which would set
  scaling to 1.0.

1) In savescreen(), if the vmode is not found, explicitly set
   pixels to NULL rather than leaving it uninitialized.
2) Ensure that currmode is never left as _ORIGMODE (which is not
   a defined mode, so can result in vmode not being found).

There's no good argument for this aside from "it feels more right".

Properly initialize sixel mask width/height.
Free sx_mask->bits when finished.

These were broken by the PPM feature commit 6f97dfce

This mirrors commit 1dc4c22a about a year ago that optimized window
dragging, and performs basically the same check (removed a week ago
with commit a59aba35)

Now that bitmap_drv_request_some_pixels() just calls
bitmap_drv_request_pixels(), there's no point in calling expose_rect()
when ev->xexpose.count isn't zero.

- Only call cb_flush() if a new rect was queued.
- Ensure bitmap_drv_request_some_pixels() is only called once in
  response to an expose request.

This should fix issue #565.

Also, do not try to display frames where the scaled height or width
is less than the frame bitmap height or width.

sdl_getscaling() does not require vstatlock.  Move it out.