add doc about effects for capabilities

[sonichi]

Why are these changes needed?

• Explain the effect of a capability in docstr.
• Move tests about capabilities.
• Use correct path for import.
• Use pull_request as the trigger of workflow.

Related issue number

Checks

• I've included any doc changes needed for https://microsoft.github.io/autogen/. See https://microsoft.github.io/autogen/docs/Contribute#documentation to build and test documentation locally.
• I've added tests (if relevant) corresponding to the changes introduced in this PR.
• I've made sure all auto checks have passed.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 54.69%. Comparing base (f749dee) to head (dd8079b).

Additional details and impacted files

@@             Coverage Diff             @@
##             main    #1842       +/-   ##
===========================================
+ Coverage   35.90%   54.69%   +18.78%     
===========================================
  Files          63       63               
  Lines        6637     6608       -29     
  Branches     1456     1581      +125     
===========================================
+ Hits         2383     3614     +1231     
+ Misses       4063     2696     -1367     
- Partials      191      298      +107     

Flag	Coverage Δ
unittests	54.66% <100.00%> (+18.75%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[sonichi]

@LittleLittleCloud I changed the trigger back to pull_request to address a security requirement.

[LittleLittleCloud]

@sonichi

OK sounds good, that might prevent PR from forked repo to consume openai secrets?

[sonichi]

@sonichi

OK sounds good, that might prevent PR from forked repo to consume openai secrets?

Yes. So if a PR requires an openai test, it needs to be made from a branch within this repo.