Upgrade markupsafe

[iurisilvio]

Description

Fixes #2476

I bumped versions of some dependencies.

• Old Jinja2 doesn't work with new markupsafe, so I upgraded Jinja2.
• Old Flask doesn't work with new Jinja2, so I upgraded Flask.
• Flask requires minimal versions of click, itsdangerous and werkzeug, so I upgraded them.

Upgrades unrelated to markupsafe to make examples work:

• protobuf was pinned to a conflicted version because of some transitive dependency changed:

The conflict is caused by:
    The user requested protobuf==3.18.3
    googleapis-common-protos 1.52.0 depends on protobuf>=3.6.0
    opentelemetry-proto 1.20.0 depends on protobuf<5.0 and >=3.19

• wrapt < 1.14 is incompatible with Python 3.11 (https://github.com/GrahamDumpleton/wrapt/blob/develop/docs/changes.rst#version-1140), I upgraded them to be able to run examples.

We could at least have a CI action to install these example requirements file to check if they're not outdated.

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

The dependencies are used only for build and tests.

• Test A

Does This PR Require a Contrib Repo Change?

Answer the following question based on these examples of changes that would require a Contrib Repo Change:

• The OTel specification has changed which prompted this PR to update the method interfaces of opentelemetry-api/ or opentelemetry-sdk/

• The method interfaces of test/util have changed

• Scripts in scripts/ that were copied over to the Contrib repo have changed

• Configuration files that were copied over to the Contrib repo have changed (when consistency between repositories is applicable) such as in

  • pyproject.toml
  • isort.cfg
  • .flake8

• When a new .github/CODEOWNER is added

• Major changes to project information, such as in:

  • README.md
  • CONTRIBUTING.md

• Yes. - Link to PR:

• No.

Checklist:

• Followed the style guidelines of this project
• Changelogs have been updated
• Unit tests have been added
• Documentation has been updated

[iurisilvio]

The CI failure is related to #3611.