TCS-11: Add eslint-plugin-no-barrel-files rule to react config

[brettcutt-aligent]

Description of the proposed changes
Adds eslint-plugin-no-barrel-files to the shared react ESLint config so every consuming project picks up barrel-file enforcement without configuring it locally.

• Before: projects using eslintConfigs.react had no rule against barrel files; export * from … and re-exports of imported variables were silently allowed.

  // components/AddressForm/index.ts — passed lint
  export * from './AddressFields';
  export { default } from './AddressFields';

• After: any such file errors with no-barrel-files/no-barrel-files (Do not use export all or Do not re-export imported variable), via the plugin's flat/recommended config.

  // components/AddressForm/index.ts — now fails lint
  export * from './AddressFields';
  // ^ 1:1  error  Do not use export all (`export * from ...`)         no-barrel-files/no-barrel-files
  export { default } from './AddressFields';
  // ^ 2:1  error  Do not re-export imported variable (`./AddressFields`)  no-barrel-files/no-barrel-files

  Consumers should import from the source file directly instead:

  import AddressFields, { type AddressFieldsClassNames } from './AddressFields';

Screenshots (if applicable)
Symlinked and tested on the Takeflight project

Other solutions considered (if any)

Notes to PR author

⚠️ Please make sure the changes adhere to the guidelines mentioned in our contribution guide.

Notes to reviewers

ℹ️ When you've finished leaving feedback, please add a final comment to the PR tagging the author, letting them know that you have finished leaving feedback

[kai-nguyen-aligent]

LGTM. However, is there any reason not to apply this to the base config also?

[brettcutt-aligent]

LGTM. However, is there any reason not to apply this to the base config also?

@nettree the scope of the task is to apply the rule to react, but should we instead apply it to the base?

[nettree]

LGTM. However, is there any reason not to apply this to the base config also?

@nettree the scope of the task is to apply the rule to react, but should we instead apply it to the base?

Sure @brettcutt-aligent

If @kai-nguyen-aligent and @aligent-lturner agree with this rule to be applied to all our TS projects then I'm happy with it

[aligent-lturner]

LGTM. However, is there any reason not to apply this to the base config also?

@nettree the scope of the task is to apply the rule to react, but should we instead apply it to the base?

Sure @brettcutt-aligent

If @kai-nguyen-aligent and @aligent-lturner agree with this rule to be applied to all our TS projects then I'm happy with it

Fine with me

[nettree]

@brettcutt-aligent let's move this to base :)

[kai-nguyen-aligent]

LGTM!

[nettree]

Awesome, let's go :)