chore(deps): Renovate dependency updates

[calvincestari]

This is a collection of the following dependency update PRs to avoid multiple subtree push/pulls and having to update each dependency PR once main is updated due to the merge rules.

• chore(deps): replace dependency babel-eslint with @babel/eslint-parser 7.11.0 #160
• chore(deps): update dependency node-sass to v7.0.3 #161
• chore(deps): update secops orb to v2.0.3 #162
• chore(deps): update vue monorepo to v2.7.15 #163
• chore(deps): update dependency @rollup/plugin-node-resolve to v15 #164
• chore(deps): update dependency @rollup/plugin-replace to v5 #165
• chore(deps): update dependency @rollup/plugin-typescript to v11 #166
• chore(deps): update dependency @vue/eslint-config-airbnb to v7 #167
• chore(deps): update dependency @vue/test-utils to v2 #168
• chore(deps): update dependency eslint to v8 #169

[calvincestari]

We have CI tests that validate any changes to the GraphQLCompiler JS package but nothing automated for the documentation generator, so I have manually confirmed that there are no errors during the swift run DocumentationGenerator command from the docs renderer package changes.

[AnthonyMDev]

If there are changes to the JS Frontend package, we need to actually run rollup and then run the Swift codegen tests with the new code in the ApolloCodegenFrontendBundle. If the tests pass after doing that, I'm good to ship this!

[calvincestari]

If there are changes to the GraphQL-js package, we need to actually run rollup and then run the Swift codegen tests with the new code in the ApolloCodegenFrontendBundle. If the tests pass after doing that, I'm good to ship this!

That's a very good point but there are no changes to the bundle after running the auto_rollup script so nothing to re-test.