[Epic:.NET] Align all the build-in DTOs that appear in the UI under the entity-related-modules (e.g. CustomerFindManyArgs) VS the actual dotnet DTOs

[mulygottlieb]

We need to decide which "way" to align - either change the dotnet generated code to use the same DTOs we use for Nest (that appear in the UI), or - change the auto-created-DTOs in the server according to the chosen tech-stack for the service (align the blocks and UI to the actual generated code).
This needs to be discussed internally first (Mango)

[overbit]

This needs to be reviewed as the current generation is not using the same DTOs @mulygottlieb @morhag90.

Ideally we will replace the currently generated DTOs with the ones defined in the amplication platform

[mulygottlieb]

Moving this back into "Todo" until we have the discussion which side to align to which side

[mulygottlieb]

Tech notes for implementation:
Server:

• Filter out GQL-only DTOs in the server in the ModuleDTO Resolver

Dotnet DSG:

• Rename non-GQL DTOs to the names we have in the server
• Change the [Entity]IdDto - rename, do not inherit in the [Entity] DTO and instead add the id with its id-type directly

Dotnet Plugins

• Review existing dotnet plugins for use of the DTOs names and in particular in the IdDto

[morhag90]

Passed QA:

Forbbiden:

Authorize + FindOne => Not Found:

Create One entity:

FindMany:

Get one entity:

Create one entity with another entity relation:

The other side:

[mulygottlieb]

Retuning to qa just to qa the dto filtering in the server as well.