Bug: Order of operations inside ModuleFederationPlugin

[jbroma]

Description

Inside of ModuleFederationPlugin we have this piece of code:

// ...
new container.ModuleFederationPlugin({
      ...this.config,
      filename:
        this.config.filename ?? this.config.exposes
          ? `${this.config.name}.container.bundle`
          : undefined,
// ...

Filename should evaluate to this.config.filename, but instead it evaluates to name.container.bundle whenever this.config.exposes is present, which is clearly an order of operations issue.

When using ModuleFederation, ScriptManager's resolver use .container.bundle as a way to differentiate other chunks from container chunks. Therefore before fixing this issue, we need to find a way to differentiate them differently.