feat: add new option for set http module as global module

[chenc041]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

add new option for set axios as global module

Does this PR introduce a breaking change?

• Yes
• No

Other information

[micalevisk]

we should expose a .forRoot/.forRootAsync static method instead of changing the .register. See https://docs.nestjs.com/fundamentals/dynamic-modules#community-guidelines

[chenc041]

static forRoot(config: HttpModuleOptions): DynamicModule {
    return {
      module: HttpModule,
      global: config.global,
      providers: [
        {
          provide: AXIOS_INSTANCE_TOKEN,
          useValue: Axios.create(config),
        },
        {
          provide: HTTP_MODULE_ID,
          useValue: randomStringGenerator(),
        },
      ],
    };
  }

you mean like this ?

[micalevisk]

yeah, I think so. But global must be true

and a .forRootAsync as well

[chenc041]

yeah, I think so. But global must be true

and a .forRootAsync as well

ok, I has changed