Interesting… it should take a moment, not a while.
Re: the results of your blacklist query above: My (functioning) wireless laptop produces the identical blacklist results, word for word.
I’m still struck by this entry you’ve shared:
Device-2 (presumably your wireless device) shows “driver: N/A” - which suggest to me (a newbie for sure) that you’ve not yet gotten a wireless driver properly installed. 
As @SomeGuy said his blacklist looks the same. So the following should not make a point if its the same error. But if the driver install and reboot not bring your wifi up take a look at this:
As you see there is BCM43** blacklisted. So I would suggest to delete this.
To find the file you have to go you can typ this (perhaps its called mhwd-network.conf):
grep -l bcm43xx /etc/modprobe.d/*
Then open it with nano (or an other editor) and delete these line.
sudo nano /etc/modprobe.d/*yourfile*
After deleting these line you can save the file in nano with crtl+o and exit with ctrl+x. After a reboot the driver should be loaded automatically.
Good luck, … I am afk for today 
Just to clarify… while I confirm that I see the identical list of eight (8) blacklist’ed entries, my wifi is in fact functioning and I’m not getting any errors (actually, my download speeds on this laptop are running around 50Mbps at the moment).
It’s clearly worth a try to follow @kisun’s guidance as he’s far more Linux-savvy than me, but since those same blacklist entries aren’t stopping my BCM4331 wireless adapter from functioning, I’d be surprised if they were stopping your BCM43142 from functioning. Still worth a try.
Are you seeing any change based on inxi results with respect to your Device-2 (wireless broadcom device) showing a driver (instead of N/A) since you’ve followed steps thus far?
its still downloading currently at 84%,i haven’t done a system upgrade in a long long time, ill check after the download is finish
Ah, I thought it was just the wifi driver you were downloading … not an entire system upgrade.
Yes, if you’re running kernel 5.10 you’ve likely got a lot of upgrading to do. Latest I’ve got on a rolling basis is now 5.19 … perhaps this might also provide you with a current platform on which to get your wifi driver working. Keep us posted.
i installed the linux-rt-broadcom-wl package , it gave the following output which has an error in it
Packages (2) linux519-rt-5.19.0_rt10-3 linux519-rt-broadcom-wl-6.30.223.271-3
Total Download Size: 128.40 MiB
Total Installed Size: 133.47 MiB
:: Proceed with installation? [Y/n] y
:: Retrieving packages...
linux519-rt-5.19... 127.0 MiB 172 KiB/s 12:34 [######################] 100%
linux519-rt-broa... 1477.2 KiB 127 KiB/s 00:12 [######################] 100%
Total (2/2) 128.4 MiB 172 KiB/s 12:46 [######################] 100%
(2/2) checking keys in keyring [######################] 100%
(2/2) checking package integrity [######################] 100%
(2/2) loading package files [######################] 100%
(2/2) checking for file conflicts [######################] 100%
(2/2) checking available disk space [######################] 100%
:: Processing package changes...
(1/2) installing linux519-rt [######################] 100%
Optional dependencies for linux519-rt
wireless-regdb: to set the correct wireless channels of your country
[installed]
(2/2) installing linux519-rt-broadcom-wl [######################] 100%
:: Running post-transaction hooks...
(1/5) Arming ConditionNeedsUpdate...
(2/5) Updating module dependencies...
(3/5) Install DKMS modules
==> ERROR: Missing 5.19.0-3-rt10-MANJARO kernel headers for module rtl8821ce/1.0.5.r130.gca204c6.
(4/5) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux519-rt.preset: 'default'
-> -k /boot/vmlinuz-5.19-rt-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.19-rt-x86_64.img
==> Starting build: 5.19.0-3-rt10-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
-> Running build hook: [resume]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.19-rt-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux519-rt.preset: 'fallback'
-> -k /boot/vmlinuz-5.19-rt-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.19-rt-x86_64-fallback.img -S autodetect
==> Starting build: 5.19.0-3-rt10-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: qla2xxx
==> WARNING: Possibly missing firmware for module: qed
==> WARNING: Possibly missing firmware for module: qla1280
==> WARNING: Possibly missing firmware for module: bfa
==> WARNING: Possibly missing firmware for module: xhci_pci
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
-> Running build hook: [resume]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.19-rt-x86_64-fallback.img
==> Image generation successful
(5/5) Updating Grub-Bootmenu
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-5.19-rt-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.19-rt-x86_64.img
Found initrd fallback image: /boot/initramfs-5.19-rt-x86_64-fallback.img
fgrep: warning: fgrep is obsolescent; using grep -F
Found linux image: /boot/vmlinuz-5.15-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.15-x86_64.img
Found initrd fallback image: /boot/initramfs-5.15-x86_64-fallback.img
fgrep: warning: fgrep is obsolescent; using grep -F
Found linux image: /boot/vmlinuz-5.10-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.10-x86_64.img
Found initrd fallback image: /boot/initramfs-5.10-x86_64-fallback.img
fgrep: warning: fgrep is obsolescent; using grep -F
Found linux image: /boot/vmlinuz-5.4-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.4-x86_64.img
Found initrd fallback image: /boot/initramfs-5.4-x86_64-fallback.img
fgrep: warning: fgrep is obsolescent; using grep -F
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Found memtest86+ image: /boot/memtest86+/memtest.bin
done
specifically:
==> ERROR: Missing 5.19.0-3-rt10-MANJARO kernel headers for module rtl8821ce/1.0.5.r130.gca204c6.
the inxi command still gives N/A for the wireless device driver.
well i guess a reboot might be needed at this point, so lets see if something changes
Definitely, always reboot after a kernel upgrade - or other significant system changes, for good measure. Safe to assume you’re now on kernel 5.19?
(FWIW, I thought rtl8821 was a Cudy wireless dongle, not an internal broadcom card)
it detected the driver
Device-2: Broadcom BCM43142 802.11b/g/n vendor: Dell Wireless 1704 802.11n
+ BT 4.0 driver: wl v: kernel modules: bcma pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 bus-ID: 09:00.0 chip-ID: 14e4:4365 class-ID: 0280
yes i think i am on kernel 5.19 now.
and this should prove that im on kernel 5.19
CPU: dual core Intel Core i3-2370M (-MT MCP-)
speed/min/max: 1841/800/2400 MHz
Kernel: 5.19.0-3-rt10-MANJARO x86_64 Up: 4m
Mem: 1213.8/3835.9 MiB (31.6%) Storage: 698.64 GiB (15.6% used) Procs: 265
Shell: Bash inxi: 3.3.22
Progress! And is wifi running at this point?
i have no idea how i try to connect to the wifi tbh, any advice?
[djamel@djamel ~]$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp5s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 78:45:c4:b3:f8:67 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.39/24 brd 192.168.1.255 scope global dynamic noprefixroute enp5s0
valid_lft 43145sec preferred_lft 43145sec
inet6 fe80::7bd7:703f:670c:d4f2/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: wlp9s0: <NO-CARRIER,BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000
link/ether f2:89:25:9a:c2:0a brd ff:ff:ff:ff:ff:ff permaddr e0:06:e6:d2:86:b9
4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:0a:c0:d9:b7 brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
valid_lft forever preferred_lft forever
[djamel@djamel ~]$
ip a command gave the above output
the 3: wlp9s0, i didnt have that before, but that has a role in connecting to the wifi i guess
If you’ve got an ethernet hard wire connection up and running, then you can probably just click on the Network icon on the bottom of your screen, and from there accomplish establishing a wi-fi connection most directly.
— otherwise ----
Go to “System Settings” in your main menu (typically under “Settings” not “System”)
Then under “Network” category, select “Connections” …
Then under “Wi-Fi” you’ll need to find the available connections, selecting your home wifi router/password…
To see available connections, on my KDE Plasma desktop environment, there’s a “+” sign at the bottom of the Connections panel. Click on the “+” then select “Wi-fi” and the “Create” button.
You’ll see a screen with the top choice being “SSID” - click on the pull down arrow and you should then see a list of all the available wi-fi connections (your home wi-fi included).
But just seeing a list of available wifi connections would indicate that your wifi adapter has been identified, has a driver, and is functioning.
Sounds like meaningful progress. You are on the right track … but I’m not seeing the little drop-down triangle at the right edge of the SSID input space. This suggests your wi-fi adapter is not up and running just yet.
Have you rebooted again since upgrading and trying once again to install the updated driver?
i did reboot after installing the driver, and after rebooting i didnt install anything else.
ima reboot right now, maybe that might fix something.
If you haven’t done so yet since upgrading your kernel, I would suggest reinstalling the latest 5.19 driver too. Can’t hurt and might help. 
warning: linux519-rt-broadcom-wl-6.30.223.271-3 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...
after the kernel update i did install the re-broadcom-wl for the linux 5.19, so i dont think that would solve anything
however in the ip a command
the state of the device is DORMANT, i think if we can manage to get it to UP the problem should be solved.
whats ur opinion?
That sounds like the solution, indeed. Dormant would seem to indicate that the device is now recognized and has a matching driver. Let’s explore how to wake it up…
3: wlp9s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether c6:8a:4e:42:a4:a9 brd ff:ff:ff:ff:ff:ff permaddr e0:06:e6:d2:86:b9
i did set the state up with the command sudo ip link set wlp9s0 state UP, but there is no drop down on the SIDD, but keep in mind that when i rebooted the laptop (after setting the state to up) the state went back to DORMANT.
Interesting. I’ve been exploring various ways to address a DORMANT state and haven’t found a closely analogous circumstance to yours yet.
What do you get if you perform rfkill list?
Does it indicate you have any lock/blocks in effect?