improve FunctionMesh labels

[tpiperatgod]

(If this PR fixes a github issue, please add Fixes #<xyz>.)

Fixes #449

(or if this PR is one task of a github issue, please add Master Issue: #<xyz> to link to the master issue.)

Master Issue: #

Motivation

Explain here the context, and why you're making that change. What is the problem you're trying to solve.

Modifications

Current labels：

    "app":       AppFunctionMesh,
    "component": ComponentFunction,
    "name":      function.Name,
    "namespace": function.Namespace,

New labels：

    "app.kubernetes.io/name":            jobName, // <resource name> + "-function"
    "app.kubernetes.io/instance":        jobName,
    "compute.functionmesh.io/app":       AppFunctionMesh,
    "compute.functionmesh.io/component": ComponentFunction,
    "compute.functionmesh.io/name":      function.Name,
    "compute.functionmesh.io/namespace": function.Namespace,
    // The following will be deprecated after two releases
    "app":       AppFunctionMesh,
    "component": ComponentFunction,
    "name":      function.Name,
    "namespace": function.Namespace,

Verifying this change

• Make sure that the change passes the CI checks.

(Please pick either of the following options)

This change is a trivial rework / code cleanup without any test coverage.

(or)

This change is already covered by existing tests, such as (please describe tests).

(or)

This change added tests and can be verified as follows:

(example:)

• Added integration tests for end-to-end deployment with large payloads (10MB)
• Extended integration test for recovery after broker failure

Documentation

Check the box below.

Need to update docs?

• doc-required

  (If you need help on updating docs, create a doc issue)

• no-need-doc

  (Please explain why)

• doc

  (If this PR contains doc changes)

[nlu90]

We may need to make a release for this PR to unblock some internal projects