update memory_bank related naming to vector_db in notebook

[wukaixingxp]

Updated memory related naming in section 2.3. RAG Agent to vector_db

Previously:

2.3. RAG Agent
In this example, we will index some documentation and ask questions about that documentation.

The tool we use is the memory tool. Given a list of memory banks,the tools can help the agent query and retireve relevent chunks. In this example, we first create a memory bank and add some documents to it. Then configure the agent to use the memory tool. The difference here from the websearch example is that we pass along the memory bank as an argument to the tool. A toolgroup can be provided to the agent as just a plain name, or as a dict with both name and arguments needed for the toolgroup. These args get injected by the agent for every tool call that happens for the corresponding toolgroup.

Now:

2.3. RAG Agent
In this example, we will index some documentation and ask questions about that documentation.

The tool we use is the rag_tool. Given a list of vector_db,the tools can help the agent query and retireve relevent chunks. In this example, we first create a vector_db and add some documents to it. Then configure the agent to use the rag_tool. The difference here from the websearch example is that we pass along the vector_db_ids as an argument to the tool. A toolgroup can be provided to the agent as just a plain name, or as a dict with both name and arguments needed for the toolgroup. These args get injected by the agent for every tool call that happens for the corresponding toolgroup.

• Addresses issue (#issue)

Test Plan

Please describe:

• tests you ran to verify your changes with result summaries.
• provide instructions so it can be reproduced.

Sources

Please link relevant resources if necessary.

Before submitting

• This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
• Ran pre-commit to handle lint / formatting issues.
• Read the contributor guideline,
  Pull Request section?
• Updated relevant documentation.
• Wrote necessary unit or integration tests.