LICENSE and CONTRIBUTING files still mention and link to FlowForge

[Steve-Mcl]

Current Behavior

Most of the FlowFuse repositories still call out FlowForge and link to https://flowforge.com in the LICENSE and CONTRIBUTING files.

NOTE: The LICENSE should still refer to FlowForge as the legal entity

@ZJvandeWeg this may be something you wish to clarify and offer precise wording on before the issue is undertaken?

Expected Behavior

LICENSE and CONTRIBUTING files: should link to https://flowfuse.com

CONTRIBUTING files: should say FlowFuse not FlowForge

LICENSE files: Should clarify FlowForge is the legal entity of FlowFuse

Steps To Reproduce

No response

Environment

• FlowFuse version: 2.1-git

Have you provided an initial effort estimate for this issue?

I have provided an initial effort estimate

### Tasks
- [ ] Update basic docs usage of FlowForge to FlowFuse
- [ ] Update FlowForge in License files in all repos to state FlowFuse
- [ ] Updated Local Installation doc to use FlowFuse paths
- [ ] Update docs and base configuration to use FlowFuse.yml (or something more generic)

[ZJvandeWeg]

@Steve-Mcl its in the website footer: FlowForge Inc. DBA FlowFuse

[Steve-Mcl]

@ZJvandeWeg following up on your recent rename announcement, can we update these yet?

[ZJvandeWeg]

@Steve-Mcl FlowFuse Inc indeed. Thanks!

[Steve-Mcl]

I marked this as a size-1. Looking closer, there are a LOTS of places (like docs, configuration / yaml, installation procedures, live code, tests and other places) where flowforge is still used. i.e. This is not a simple search+replace, but more of a strategic scalpel job.

The FlowFuse core repo alone...

This will need breaking down into separate tasks.

Any references that impact related repositories (i.e. file names, URLs, etc) will need to be assessed on a case by case basis and raised as child tasks.