Use full project path for issueMoveList mutation

What does this MR do?

Related to #247911 (closed)

When moving issues between lists in a subgroup board, the variable projectPath for issueMoveList only contains the parent group and subgroup path so the mutation fails and returns the error

"The resource that you are attempting to access does not exist or you don't have permission to perform this action"

This error is triggered by trying to access the issue in the wrong parent and was introduced by splitting the issue's path.

This MR modifies the argument passed to split() in action.js:240 to assign the issue's full path to the first constant and use it as the mutation variable projectPath.

issuePath = 'gitlab-org/test-subgroup/test-sub-project#1'

// before
issuePath.split(/[/#]/);
=> ["gitlab-org", "test-subgroup", "test-sub-project", "1"]

// after
issuePath.split(/[#]/);
=> ["gitlab-org/test-subgroup/test-sub-project", "1"]

Screenshots

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• Tested in all supported browsers
• Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team