[feature] Add a "Referer" variable in notification body

[huanghe2015]

Version and OS
0.49.3

Is your feature request related to a problem? Please describe.
No.

Describe the solution you'd like
Some kinds of data were loaded by AJAX, but we need to click the source page directly to view it(I'm too lazy...), the current way to archive it is to customize the watches' notification body text, but it isn't so convenient in daily use. As the source page can be found by the "Referer" section in the request header or the response header, it can be read to the variable store and used in the notification's body text.

Describe the use case and give concrete real-world examples
Here is a watch I'm the most frequently used.

curl 'https://www.pudong.gov.cn/zwgk-search-front/api/data/affair' \
  -H 'Accept: application/json, text/plain, */*' \
  -H 'Accept-Language: zh-CN,zh;q=0.9,en-US;q=0.8,en;q=0.7,zh-TW;q=0.6' \
  -H 'Connection: keep-alive' \
  -H 'Content-Type: application/json;charset=UTF-8' \
  -b '_pk_testcookie.300.0950=1; 0zaLpREBxJs7S=60fz_zS9_a_tPKaTaHKCFnxdGcURgwdlk0l7LBPjoF5VZVeu2PTjRsfQJ7ZsagvdJkAnuhBR2KJzN9NYfDMXvMZG; 0zaLpREBxJs7O=602hyY7zZILH1fJ6qxTM31cFGBqKwsi24AQxPgDg0fUtPvNgEccCAxWBD2_CQo2Ng65iZ7DvQSt3RmPs_dcsLvYa; zh_choose=s; _pk_ses.300.0950=1; 0zaLpREBxJs7T=0Fg.4aB2xuteEDaKTyZuX.rnZ7gJhZn5wPelLbuMvsdJGcS5f_WsW.Ld7RJPRHSzb2eVfAdmwMT5PSYejvFd9ZCnGbU1Oh2bzroP0fcFiU8AOzfen3D06TCxUZXrmkUyhs04N4kFwUDt4YyoGfGXmDGKxgNxpXeZFqHwCfcFev44dAFSILFlxzYXdjz27rXkfokYLe9QX8_3DmeD2mCbNM6v7Bn5RhnM2YJCmPgUdwFGeuy9VRGviUiDfpQIGx7l8wpmelZa_cGbpv7irucx2daoQlehTeMzTabqXKaLDAlxtF0glt8uF17VnEfZ3vwQZ5tztsM9QKxvh3KrFqJaD70HG.1Bu58G0W1cBWCFjZYGR0PA3VMzDUTocFhI5CWpy3aY38TuY1ParZ8u2kihiXqxIqU8BQszT1XBt9spmCh3; 0zaLpREBxJs7P=0shrB4NQGg0nZ.UMJVyG14_cALNUpGGEbylCY8keahuK7gGxju1dyjipYOz6ehlfg3GC573savGV811ANeVr_1ScwHX7u8ZfE8G0B8A4v.WmG0zP_92_czbph4YdGLcK6wBE9r626YF5W8cQDS9Qdr0OrruC2XihY72ArAM585Vr4n7PooWahDLjYxFFPyvAR5mw0KTXHs8wRwgrWZHSFKzsiijopZAzdqsEMU5c7aKwpJk197HwE93j_QDqziM0MOASNc_sbiXIOWTttgrpjz_CnodQMPGBaSLoeb.sYCKjTQ021f_7mHCW.HSONx1TgWvsIFGPSg7JJHDJPIVRpB.mNGatjzAzVnj_IqzwJiTkTPmAbR6hnw0VsniZOpqIBOvvrs3AC21oh0rVnlWu99NfgO0ODl3FeCB6JsEkaNUV; _pk_id.300.0950=6e14e731a1a33274.1735659033.2.1741770990.1741770965.' \
  -H 'DNT: 1' \
  -H 'Origin: https://www.pudong.gov.cn' \
  -H 'Referer: https://www.pudong.gov.cn/zwgk/zwgk_zfxxgkml_abmdr14_zfbm_rsjybj/' \
  -H 'Sec-Fetch-Dest: empty' \
  -H 'Sec-Fetch-Mode: cors' \
  -H 'Sec-Fetch-Site: same-origin' \
  -H 'User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36' \
  -H 'sec-ch-ua: "Chromium";v="134", "Not:A-Brand";v="24", "Google Chrome";v="134"' \
  -H 'sec-ch-ua-mobile: ?0' \
  -H 'sec-ch-ua-platform: "macOS"' \
  -H 'sec-gpc: 1' \
  --data-raw '{"channelList":["14434"],"pageSize":2000}'

[dgtlmoon]

Hmmm yeah that ones a real edge case, i think for now it wont be solved but thanks for the report