Vote on which instrumentations to implement the migration plan!

Based off of the recent discussion on alleviating some of the implementation burden of implementing the migration plan for instrumentations moving to new semantic conventions, we are now allowed to choose a subset of instrumentations to implement this for. Please comment here on the preferences for "important instrumentations" that we should include as part of the migration plan. Keep in mind non-http instrumentations are included because this affects their eventual migration. A couple of things to also consider:

1. We can iterate on this list, where we can INCLUDE instrumentations in this list as we see fit but we most likely do not want to REMOVE ones that we already decide to be important.
2. Once we decide on a preliminary set of instrumentations, we can begin implementing migration plans for them INDIVIDUALLY.
3. For instrumentations NOT included in the set, we can begin to discuss whether we want to allow for contributions that update PARTIALLY to new semantic conventions.

For starters, I vote:

opentelemetry-instrumentation-aiohttp-client
opentelemetry-instrumentation-asgi
opentelemetry-instrumentation-django
opentelemetry-instrumentation-fastapi
opentelemetry-instrumentation-httplib
opentelemetry-instrumentation-httpx
opentelemetry-instrumentation-flask
opentelemetry-instrumentation-psycopg2
opentelemetry-instrumentation-requests
opentelemetry-instrumentation-sqlalchemy
opentelemetry-instrumentation-requests
opentelemetry-instrumentation-urllib
opentelemetry-instrumentation-urllib3
opentelemetry-instrumentation-wsgi

Start by reading the linked semantic-conventions discussion and this issue's comment thread, then review the listed Python instrumentations. Done means agreeing on a preliminary set of important instrumentations and establishing which individual migration plans should be implemented next.