nir: Drop imov/fmov in favor of one mov instruction

The difference between imov and fmov has been a constant source of
confusion in NIR for years.  No one really knows why we have two or when
to use one vs. the other.  The real reason is that they do different
things in the presence of source and destination modifiers.  However,
without modifiers (which many back-ends don't have), they are identical.
Now that we've reworked nir_lower_to_source_mods to leave one abs/neg
instruction in place rather than replacing them with imov or fmov
instructions, we don't need two different instructions at all anymore.

Reviewed-by: Kristian H. Kristensen <hoegsberg@google.com>
Reviewed-by: Alyssa Rosenzweig <alyssa@rosenzweig.io>
Reviewed-by: Vasily Khoruzhick <anarsoul@gmail.com>
Acked-by: Rob Clark <robdclark@chromium.org>
10 jobs for !826 with review/nir-untyped-mov in 8 minutes and 11 seconds (queued for 2 seconds)
detached
Status Job ID Name Coverage
  Containers Build
passed #316244
debian

00:00:21

 
  Build+Test
passed #316246
meson-clang

00:05:15

passed #316250
meson-clover

00:07:49

passed #316249
meson-main

00:02:11

passed #316245
meson-swr-glvnd

00:03:38

passed #316251
meson-vulkan

00:02:49

passed #316253
scons-llvm

00:03:52

passed #316252
scons-nollvm

00:02:14

passed #316247
scons-swr

00:03:22

passed #316248
scons-win64

00:05:33