[Bug]: processing in http-service-csharp affect other emitters

[weidongxu-microsoft]

Describe the bug

Enable http-service-csharp causes change of TCGC crossLanguageDefinitionId (which is generated from Namespace/Interface/Operation or Model) in http-client-java
allenjzhang/typespec-e2e-demo@d48c548

E.g. Todo.TodoItems.Attachments.createFileAttachment becomes Todo.TodoItems.Attachments.AttachmentsOperations.createFileAttachment, with http-service-csharp enabled.

Not sure if the cause is this code
https://github.com/microsoft/typespec/blob/main/packages/http-server-csharp/src/service.ts#L1344-L1354

        const iface: Interface = program.checker.createAndFinishType({
          node: undefined as any,
          sourceInterfaces: [],
          decorators: [],
          operations: createRekeyableMap(nsOps),
          kind: "Interface",
          name: `${target.name}Operations`,
          namespace: target,
          entityKind: "Type",
          isFinished: true,
        });

I kind of assume the processing of emitters should be independent from each other. I didn't expect processing in one emitter would affect other emitters.

Reproduction

Generate typespec-e2e-demo/todoApp with both "http-service-csharp" and "http-client-java". See the content of "todoApp/clients/java/src/main/resources/META-INF/todo_apiview_properties.json" file.

Checklist

• Follow our Code of Conduct
• Check that there isn't already an issue that request the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion.
• The provided reproduction is a minimal reproducible example of the bug.

[markcowl]

This should be fixed in #5417