[NVFP4] Expand dynamic types, clean-up conditions

[dsikka]

Summary:

• Expand dynamic to include an enum local - with this change, the following conditions are now accepted:

1. If dynamic is True --> all parameters are generated on the fly
2. If dynamic is False --> all parameters are statically generated and saved to disk
3. If dynamic is local --> all local quantization parameters are generated on the fly

• Expand nvfp4a16 to use tensor_group --> this strategy is now assocciated with the initialization of global_scales for weight and activations, not is_fp4
• Clean-up/re-order init conditions
• Expand testing

Testing

• All existing tests pass + new test cases
• LLM Compressor Test cases pass
• NVFP4/NVFP4A16 recipes work as expected

[brian-dellabetta]

Few comments

[kylesayrs]

As long as we feel confident that there's no expected behavior resulting from "local" being evaluated to True, then this looks good

[dsikka]

As long as we feel confident that there's no expected behavior resulting from "local" being evaluated to True, then this looks good

yeah I agree. Used the explicit check for quant_config for bettter readability

[brian-dellabetta]

nice nice nice