[Project Transfer Modal - Meta Issue] Allow Users To Automatically Transfer Projects To Themselves And Assign A Team

### Problem Statement

There are a lot of GitHub issues relating to project transfer but most can be boiled down to three core problems:
- project transfer can result in seemingly lost projects due to missing fields like team assignments
- project transfer does not transfer certain fields

A fourth category of problem is that project transfer is blocked at a technical level between SAAS Regions

### Solution Brainstorm

The current project transfer modal only surfaces a singular option - the email you wish to send the transfer request:

I would propose that this modal surface an option to transfer this to any organization of which you are member with an owner or manager role _in the same region_. And assign a team on transfer.

This would resolve the majority of linked issues:
- owner (https://github.com/getsentry/sentry/issues/73538, https://github.com/getsentry/sentry/issues/71943, https://github.com/getsentry/sentry/issues/64526, https://github.com/getsentry/sentry/issues/64526
- team (https://github.com/getsentry/sentry/issues/70494, https://github.com/getsentry/sentry/issues/81852, https://github.com/getsentry/sentry/issues/79477
- region (https://github.com/getsentry/sentry/issues/73899)

I would also propose the modal wording make it clear that not all linked data is transferred (https://github.com/getsentry/sentry/issues/43987, https://github.com/getsentry/sentry/issues/52316)

### Product Area

Settings - Projects

No files, tests, or entry points are named. Start by reviewing the linked project-transfer issues and locating the current project transfer modal and its same-region organization and team data flow. Done means the transfer behavior, owner and team assignment, region limitation, and incomplete-data wording are agreed and covered by tests.

Written by the indexing model from the issue text.