boards: Remove nxp board-vendor from non-NXP boards

[butok]

• Delete nxp board-vendor references from non-NXP board .yaml files.
• board.yml files already contain the correct board-vendor names.

[butok]

The CI errors (not caused by this PR) have been reported.

[jonas-rem]

Since #89024 is merged, the board catalog is being generated by the vendor info in the board.yml files. For that reason I think it would be better to change the entries to the actual vendor instead of removing them.

Probably not all vendors would notice this change in order to update the correct vendor directly. That would make the vendor info unreliable again.

[butok]

Since #89024 is merged, the board catalog is being generated by the vendor info in the board.yml files. For that reason I think it would be better to change the entries to the actual vendor instead of removing them.

Probably not all vendors would notice this change in order to update the correct vendor directly. That would make the vendor info unreliable again.

@jonas-rem

• The board.yml already has the correct information.
• No need to duplicate the board-vendor in other .yaml files, as it is already present in the main & root board.yml file.

[jonas-rem]

Since #89024 is merged, the board catalog is being generated by the vendor info in the board.yml files. For that reason I think it would be better to change the entries to the actual vendor instead of removing them.
Probably not all vendors would notice this change in order to update the correct vendor directly. That would make the vendor info unreliable again.

@jonas-rem

• The board.yml already has the correct information.
• No need to duplicate the board-vendor in other .yaml files, as it is already present in the main & root board.yml file.

Oh, yeah I confused those files.

[butok]

Thank you guys!

The CI fail is not caused by this PR:

• One CI was reported & fixed: sample: fs_sample: Build is failed for the sample.filesystem.fat_fs test case for the mm_feather board. #89305
• The other one CI fail has been reported: tests: logging: ip_k66f: build failures #89067, to be fixed by tests: logging: Allow LOG_PRINTK from user space #89115

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[dnltz]

@nordicjm this PR was not listed in the Zephyr's merge list and I'm also not authorized to merge. Can you take over or assign someone who can?