Your manifest does not currently have a display property. For further edits please open the applications windows inside a chromium browser. It will tell you exactly what you are missing. Also, the chrome lighthouse is a good tab to check for this.

Problem solved when use VPN and I think it will be due to sanctions against Iran. down with sanctions.

You wait for the web app developer to implement Chrome's WebAPK on Android feature/requirements.

From the following post: How to Remove Chrome Logo from PWA App Home Screen Link (Android O Preview)

Digging through the comments on the accepted answer from Anand dated Dec 17, 2018:

If you are asking how to avoid chrome icon, as long as your went [sic] app is fully qualifies PWA to be installed as APK, new versions of chrome won't add that icon. I've tested with chrome version 70 in Android pie . If it's a mere web page, failing to meet key PWA criteria or non PWA, chrome might add chrome icon to indicate it's a web link(depending on chrome version again)

Further research on details led me down a rabbit hole of what features exist on Chrome vs Android and the meaning of 'install' to home screen, which while it does somewhat affect end-user behavioral expectations, the implementation details are off-topic for this site.

If you can live with icon badging, you may want to try your site/webapp with Firefox for Android and see if the app UI still retains the undesirable "header".

No, you can't, at least not as useful PWAs.

Let's first take a look at the definition of Progressive Web Apps:

A progressive web app (PWA) is an app that's built using web platform technologies, but that provides a user experience like that of a platform-specific app.

Like a website, a PWA can run on multiple platforms and devices from a single codebase. Like a platform-specific app, it can be installed on the device, can operate while offline and in the background, and can integrate with the device and with other installed apps.

Source

I'll start with the "can operate while offline" specification - that is pretty much impossible to achieve on user's side with many web apps, as they rely on pulling data frequently from the internet. There are PWAs that ignore this and don't even handle lack of connection properly, but I wouldn't necessarily call them fully proper PWAs.

Then we have integration with systems. For example with notifications. This and offline handling is done with help of service workers, which you can't easily define as a user for any sort of websites either. It's also optional in theory, but if you skip such features, there's not much point of PWAs.

And lastly the most important part - ability to install it as an app on various devices. This is done by linking a manifest in the HTML, e.g.:

<link rel="manifest" href="manifest.json">

The manifest defines basic PWA info, such as icons, where the application should start, how it should be displayed, etc.

This part could perhaps be achievable by dynamically adding the tag with your own external manifest through userscript, but once again, I see no point in doing that and it's not even worth trying as adding a website to e.g. your bookmarks is basically a much more optimal equivalent.