Tgcf

**Security Update: Enhance admin protection**

- In your [configuration file (tgcf.config.yml)](https://github.com/aahnik/tgcf/wiki/How-to-configure-tgcf-%3F#example-configuration) you can now specify the usernames of admins (earlier only ids were supported)
- when tgcf is run as live, either as a bot, or user bot, the admins can run commands to change the source and destination
- setting admins is not compulsory
- if no admins are set, and you run tgcf in live mode, then no one can run commands to change the configuration. the bot/user bot will work perfectly fine as per your configuration file
------

Other features:
- animate the appearance of figlet and other small aesthetic fixes

This release brings two main changes
- Enhanced logging
- show system version/os/architecture info
- use pyfiglet for a beautiful topper
- use rich for beautified logs + rich tracebacks with syntax highlighting
- use verlat for checking if you are running the latest version of tgcf. If not, prints a message

- allow commands when deployed as userbot. (for tgcf in live mode)
- The commands [start,forward,remove,help] were available only when deployed as a bot.
- Now with the new version, `/start` for bot is equivalent to `.start` for userbot (send in Saved Messages).
similarly for the other commands.

Support regex for text filtering and replacement 136

Read wiki pages updated

https://github.com/aahnik/tgcf/wiki/How-to-use-filters-%3F

https://github.com/aahnik/tgcf/wiki/Text-Replacement-feature-explained

- You can now use the username/link/phone no of the chats safely. No need to find chat ids. 118
- The last release introduced bug 189 in delete sync, which has been fixed in this release.
- The [wiki page](https://github.com/aahnik/tgcf/wiki/How-to-configure-tgcf-%3F) for configuring tgcf has also been updated. Usernames and links are used in the example instead of chat ids.

Implement reply sync in pr 185

- add type hints as much as possible
- accept image URLs for the watermark plugin