[FE] Initialize and update dependency list components on group level

Why are we doing this work

Currently dependency list is only available on the project level.

Relevant links

Non-functional requirements

• Documentation:
• Feature flag:
• Performance:
• Testing:

Implementation plan

• frontend Create a new index.js file under ee/app/assets/javascripts/pages/groups/dependencies, similar to this file, as an initialiser for this component.
• frontend As the group level dependency.json payload won't have report job set, either this condition has to be updated or an attribute can be added from the backend to inform whether the scope is group or project.
• frontend license column won't be displayed for group level.
• frontend a new column project, displayed only for group level, could be added in this file.
• frontend dependency_location could be updated to show aggregated values as per design.
• frontend this text will change depending on the scope as per design.
• frontend sort fields will also be dependent on the scope. For group level, severity won't be used however number of projects will be added.
• frontend make sure all data attributes required in index.js are being populated.

Note: the above could use the feature flag created as part of this issue.

Testing

• Add appropriate feature specs

Verification steps