Import it by specifying address type as prefix:
SCRIPT TYPE:COMPRESSED WIF
In this example it will be p2wpkh:L48nE2detzZwEzdbw5dYTuNJy9wDqLVY92DwS7Br8NwgD6S8NiyT
You will see the address: bc1qzlcz9ckzggu8vzs2rvrsa2j9dh6w3wg4atezy6 added in wallet
there was nothing to "prohibit" a miner from spending/stealing someone else's funds
That was never true, so far as I know, miners have never been able to spend other people's funds seen in normal transactions with the right spending scripts.
A more accurate description of the situation you describe is perhaps that there was nothing to prohibit ...
Before the creation and implementation of SegWit, when all running
nodes were non-segwit, if a miner had included an ACS transaction in
his own block and he had managed to mine it, would such a block be
accepted by others nodes?
Before SegWit implementation, miners could include ACS transactions in
their blocks and all the other nodes should validate ...
This is not correct.
All segwit blocks do differently is having the witnesses (which include the signature) in a separately-hashed area. They're still an integral part of the block, and full validation cannot proceed without the witness data. Removing or altering the witness data will invalidate a block.
What this does permit is stripping the witness data ...
On 2020-12-24, Binance announced support for deposits to native segwit addresses.
Segregated witness ("segwit") refers to a soft fork that activated a series of Bitcoin improvement proposals (BIPs) in 2017. Among other things, segwit introduced two new standard output types, Pay to Witness Public Key Hash (P2WPKH) and Pay to Witness Script Hash (...
Segwit is not a separate network as mentioned in the screenshot instead its a Bitcoin protocol upgrade that provides lower transaction fees. This is also mentioned in the "Tips" section on same page in Binance.
Segwit is defined in BIP: 141,143,144,145 and 173 according to my understanding. In this context its just an address type you will use for ...
PSBT_IN_WITNESS_SCRIPT is specifically the actually executed script for a P2WSH or P2SH-P2WSH scriptPubKey being spent. It is added by an Updater who knows it.
PSBT_IN_FINAL_SCRIPTWITNESS is the witness stack needed to spend an output, including scripts, signatures, public keys, ... whatever is needed. It is created by a Finalizer, using other fields ...