Allow jitsi-meet which is marked as insecure now

This is caused by libolm used for e2ee which is an optional feature.

There's no fix in sight and the attacks are AFAIK for on the theoretical
side. I don't think that this should stop us from using Jitsi.

nixpkgs-config.nix

@@ -14,5 +14,6 @@
  "python-2.7.18.8" # Needed for some legacy customer applications.
  "ruby-2.7.8" # EOL 2023-03-31, needed for Sensu checks
  "docker-24.0.9" # Old installs still use storage driver removed in 25.x.
+ "jitsi-meet-1.0.7952" # insecure libolm but this only affects optional e2ee which we don't really support.
  ];
 }