Error states its already a distributor.

So someone / something has already tried to set it up and didn't finish the configuration.

Remove distribution as per the error message and try reconfiguring...

Not natively out of the box, but you could write routines and SSIS packages to do the replication aspect for you.

But saying you have CDC enabled, I'd just stick TX...

Your sample file has no value for P8, so the data is correct according to your PNG & provided CSV.

Log shipping or write your own ETL routines are the only thing you can do which builds a delay into synchronisation.

But you want HA via AOAG, you cannot have a...

Get a copy of a WMI query, or get a WMI browser tool and try and run it as someone with admin rights, if the query fails because the namespace...

What HA technology are you using at the SQL level?

FCI or AOAG?

On an FCI the failover with replication should be seamless in a fashion, yes it will disconnect while failing...

Stick "SQL Server Monitoring Software" into your favourite search engine, you'll be presented with a abundance of results.

What you are asking for here is a monitoring piece of software, not...

Yeah, you can ask any question here as long as it is relevant, or in any of the version specific admin forums.

A bacpac is version agnostic.  It is different from a BAK (backup).  But bacpac have limitations, size being one of them.  So if it’s a big DB then bacpac may...

Script out all the tables and data via SSMS / Tasks / Generate Scripts, then replay the output script on a 2019 server.

Make a BACPAC of the database (may or...

Replication you don't want to replicate the whole DB, that just asks for trouble.  If you do replication, make sure its the core subset of what is needed and not...

Replication or log shipping will be your only ones to be fair, although log shipping brings with it complexities about what to do if people are reporting and a log...

You could check the default trace, but depending how busy your server is that data may have been lost by now.

Look for event 93 for log growths

92 - Data File...

You would have to dump the log backups using fn_dump_dblog to see what went on, but it's going to be a huge mess.

Sounds like you need to enable auditing, but...

CreateFile error 32 is something held a handle on the file and SQL couldn't delete it.

So something was reading/writing/touching the old audit file in some way.

Best thing you can do...