feat: port eligible bambdas library examples into workflows

[GangGreenTemperTatum]

Add 16 new workflows converted from public Bambdas library (some of which i contributed myself and wanted to port over for my own usage which sparked the idea)

Summary:

Systematic conversion of high-value Bambdas to workflow format, coveringauthentication, security detection, filtering, and analysis capabilities.

New Workflows:

Authentication & Session Management

• filter-authenticated: Identifies authenticated requests with 2XX responsesusing Authorization headers or cookies
• filter-authenticated-non-bearer-tokens: Filters authenticated requestsexcluding Bearer token authentication
• filter-cookie-value: Filters requests based on specific cookie values

Security Detection

• detect-suspicious-js-functions: Identifies dangerous JavaScript functions(eval, innerHTML, setTimeout, etc.)
• deprecated-http-methods: Highlights requests using deprecated HTTP methodslike TRACE and CONNECT
• reflected-parameters: Detects parameter values reflected in response bodies
• jsonp-csp-bypass: Identifies potential JSONP-based CSP bypassvulnerabilities

Server & Technology Identification

• detect-server-names: Identifies 80+ server types from response headers(Apache, Nginx, IIS, etc.)
• detect-101-switching-protocols: Highlights HTTP 101 responses for protocolupgrades (WebSocket, HTTP/2)
• multiple-html-tags: Detects responses with multiple HTML tags that mayindicate injection

Content Analysis

• email-highlighter: Highlights requests/responses containing email addresses
• graphql-endpoints: Identifies GraphQL endpoints and queries
• annotate-soap-requests: Extracts usernames and body elements from SOAPrequests to Notes

Traffic Filtering

• filter-out-options-requests: Removes OPTIONS request noise from proxyhistory
• highlight-unencrypted-http: Highlights unencrypted HTTP traffic
• highlight-tracker-services: Identifies analytics/tracking services (GoogleAnalytics, Hotjar, Facebook, etc.)

i hope it's OK presenting these in one PR but please let me know if this is not the case :)

---

• Follow the same folder structure as other workflows (see template).
• Has a proper author name and workflow description.
• If using compiled code in JS Nodes, provide the source code for each.
• If using a 3rd party library, include its license as a comment in the source code.

[bebiksior]

Hello! This is GREAT, thanks for contributing! Please give us some time to check all of those, we will get back to you soon :D

[GangGreenTemperTatum]

Hello! This is GREAT, thanks for contributing! Please give us some time to check all of those, we will get back to you soon :D

thanks so much @bebiksior ! :) super stoked for your response on this and ofc, appreciate you acknowleding this so quickly!!

[bebiksior]

Hi :D Sorry for the delay. Have you tested those workflows? I tried installing them in Caido, and looks most of them are not valid

[GangGreenTemperTatum]

Hi :D Sorry for the delay. Have you tested those workflows? I tried installing them in Caido, and looks most of them are not valid

hey @bebiksior , my apologies for that i am unsure at the moment as to why 😕 this may have been an accidental missed commit or upgrade-related.. so sorry about that!

i'm travelling for the next few days, but ill block some time when back and ensure this is fixed and come back to you asap

[GangGreenTemperTatum]

hey @bebiksior , im going to close this mess (sorry again) and do a fresh PR to prevent the mass merge conflict dilemma