Downgrading from Safari 12 (beta) to Safari 11
This applies to Safari 12 final as well.

Overview of options


Restore your machine from backup.
Depending on methods this might take a while. You also have to make sure to turn off Auto-Update in System Preferences > App Store or your joy with good ole Safari 11 will be short lasting. You may want to this either before or while you restore. It might be a nice idea to disconnect form any network to make sure that auto-updates really do not come through. (Disconnect from ethernet or turn off Wi-Fi.) 
Re-install your OS.
That is up to the latest update but excluding  the very latest one that contains Safari 12. Which one depends on the OS you are using. This usually takes even longer and you also have to make sure to not re-install Safari 12. That means take control away from auto-update as soon as possible in the process, but be sure to manually install all other updates.
Keyhole surgery to replace really only files that are strictly necessary. This is much faster than both options above, but a bit more complicated. System Integrity Protection needs to be disabled temporarily. Procedure is outlined below.


All three cases require you to turn off auto-updating.
All three cases require you to manually install all future updates that Apple offers to you via the AppStore application, including security updates.



Keyhole surgery

for reverting the files associated to Safari 12 back to Safari 11

Simply deleting the application or replacing the application with a previous version will not work. The (beta) version 12 is not self-contained but distributed as an installer that writes a lot of files into locations different from /Applications. 

To do this downgrade you may need to have a recent backup of the system or an installer package of for example Safari 11.1.2 for Sierra (link might change quickly or disappear altogether. Also, try to use the latest applicable version) ready and an application like Pacifist. (High Sierra users might have to revert to download http://updates-http.cdn-apple.com/2018/macos/091-94327-20180709-5409BA12-7C10-11E8-84CF-4F47544C24EB/macOSUpdCombo10.13.6.dmg and extract the files from there. Still quicker than restoring from TimeMachine or a full downgrading re-sinstall.)

This is necessary because simply re-running the Safari 11.1.2 over the version 12 (beta) installation will not work either. The Safari (beta) installer writes many more files than the installer for the regular version 11.1.2 –– and these do not play nice with the installation of 11.1.2.

Therefore you need to disable SIP, open the Safari 11.1.2 package with Pacifist and find the following locations upgraded by that update. 

/Applications/Safari.app
/System/Library/Accounts/Notifications/CloudBookmarks/AccountsNotifier.bundle
/System/Library/CoreServices/SafariSupport.bundle
/System/Library/Frameworks/SafariServices.framework
/System/Library/LaunchAgents/com.apple.Safari*.plist
/System/Library/Preferences/Logging/Subsystems/com.apple.Safari*.plist
/System/Library/PrivateFrameworks/WebDriver.framework
/System/Library/StagedFrameworks/Safari


(Optional: Compare that with the installation package for the beta version.)
Delete exactly these files and folders with their contents, nothing more, nothing less.

Then restore these Safari files from backup or in this case better yet: simply re-run the 11.1.2 package installation. 

Generally, the "restore from backup" version is preferred, as Apple often forgets to really include everything needed for a self-contained installation (like the occasional info.plist file) making the re-run 11.1.2 installer method alone potentially a bit dubious.



Now that Safari 12 is out of beta and forced out onto everyone's Mac with SoftwareUpdate you of course need to uncheck "install updates automatically" in System Preferences > App Store pane.
Otherwise the above procedure will be undone in a short amount of time. 

Profit and surf on Safari 11 for as long as you can get away with not updating. Again: make sure to manually apply security and other updates if you previously relied on that procedure being done for you in the background.



The above seems to work fine for system up to macOS Sierra and High Sierra. Therefor comments regarding these procedures on Mojave are mmore than welcome.