allow specifying self-contained at http request level

[tarunKoyalwar]

Proposed Changes

• self-contained template / feature was set on global template level , but with introduction of flow and multi-protocol execution sometimes we need a combination of both ( which was original cause behind issue Issue with self contained + request annotation in flow #4788 )
• this is now resolving by allowing to specify self-contained: true at request level
• fixed issue with javascript module examples and misc updates to smtp js module
• closes Issue with self contained + request annotation in flow #4788
• closes Issue with SMTP Module and examples in js modules doc #4818

id: stripe-secret-key

info:
  name: Stripe Secret Key
  author: DhiyaneshDk
  severity: high
  tags: exposure,token,stripe

flow: http(1) && http(2)

http:
  - method: GET
    path:
      - "{{BaseURL}}"

    extractors:
      - type: regex
        part: body
        name: token
        regex:
          - 'sk_(?:live|test)_[0-9a-zA-Z]{24}'
        internal: true

  - raw:
      - |
        @Host: https://api.stripe.com:443
        GET /v1/charges?limit=1 HTTP/1.1
        Host: api.stripe.com
        Authorization: Bearer {{token}}

    self-contained: true

    matchers:
      - type: dsl
        dsl:
          - 'status_code == 200'
          - 'contains(body, "billing_details")'
        condition: and

Note

• this feature i.e specifying self-contained true at request level does not break / change any behaviour of existing templates and only acts as override of sorts at http protocol / request level
• specifying self-contained: true at global / template level marks all proto requests in template as self-contained while specifying it at http request only affects that http request[s]