Fix issues stemming from publication linting

[jonkoops]

This is a tracker issue to fix issues stemming from the publication linter introduced under #10764.

### Issues
- [ ] https://github.com/patternfly/patternfly-react/issues/10831
- [ ] https://github.com/patternfly/patternfly-react/issues/10832
- [ ] Packages do not specify a `files` field
- [ ] Packages do not have valid types
- [ ] Create a codemod to update import paths

[dlabaj]

Issues #10831 and #10832 relate to this issue.

[jonkoops]

They are linked as subtasks of this issue :)

[tlabaj]

After a meeting , the team decided to make changes in non breaking first.

[jonkoops]

Investigation is still needed to determine whether the change can be made in a non-breaking way. I would advise to test this theory against a complex dependency such as @patternfly/react-core with an existing application in order to validate this.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[jonkoops]

@tlabaj can this issue be pinned?

[kmcfaul]

#10832 is a breaking change and will need investigation to determine which exports we should define (some internal helpers are being used currently and we need to decide whether to continue to allow usage).

[jonkoops]

@kmcfaul perhaps it can be done without breaking things, but it would mean exporting everything in the package and then in the next major removing most of the exported API surface in favor of a root export. The amount of export code in the package could be reduced by adding subpath patterns.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[jonkoops]

Could this issue be pinned?

[dlabaj]

@jonkoops All set.