Documentation links in tutorials

[pseusys]

Description

Added some documentation links to some of the tutorials.

Checklist

• I have covered the code with tests
• I have added comments to my code to help others understand it
• I have updated the documentation to reflect the changes
• I have performed a self-review of the changes

[RLKRo]

Maybe use local referencing? That way it'd be possible to view the links even if they are not on github.

Instead of

[module](https://deeppavlov.github.io/dialog_flow_framework/apiref/dff.context_storages.database.html)
[object](https://deeppavlov.github.io/dialog_flow_framework/apiref/dff.context_storages.database.html#dff.context_storages.database.context_storage_factory)

use

[module](../apiref/dff.context_storages.database.html)
[object](../apiref/dff.context_storages.database.html#dff.context_storages.database.context_storage_factory)

[RLKRo]

Also, would it be possible to create a function that, like insert_installation_cell_into_py_tutorial, modifies source code of tutorials, but for creating documentation links?
So that we could write something like

[module](!link(context_storages.database))
[object](!link(context_storages.database,context_storage_factory))

and it would be replaced with

[module](../apiref/dff.context_storages.database.html)
[object](../apiref/dff.context_storages.database.html#dff.context_storages.database.context_storage_factory)

EDIT:
We could also use the same approach for dependency installation cells.

This would allow us to specify to which dependencies are required for each tutorial or to omit the installation cell:
So a string like

# !install dff[ydb], streamlit

will generate an installation cell with !python3 -m pip install -q dff[ydb], streamlit.

And if there is no such string, the installation cell will not be present in the file.

[kudep]

We add template for macros in another PR, now fix linking

[RLKRo]

Is the doc building successfully for you?

For me, the first cell is not building

I am able to fix that by removing # noqa: E501 from the cells.

Obviously, that will fail our linter.

One possible solution would be to reformat the way we insert links:

instead of

Here, [PollingTelegramInterface](https://deeppavlov.github.io/dialog_flow_framework/apiref/dff.messengers.common.interface.html#dff.messengers.common.interface.PollingMessengerInterface)
class and [telebot](https://pytba.readthedocs.io/en/latest/index.html) library are used for accessing telegram API in polling mode.

use

Here, [PollingTelegramInterface](
../apiref/dff.messengers.common.interface.html#dff.messengers.common.interface.PollingMessengerInterface
) class and [telebot](
https://pytba.readthedocs.io/en/latest/index.html
) library are used for accessing telegram API in polling mode.

Unfortunately, that is still 105 characters.

Seems like the easiest solution is to wait for an implementation of the aforementioned tutorial patterns.

[RLKRo]

I really like mddoclink. Makes it difficult to insert an incorrect link:

[pseusys]

Waiting for #144