fix(nms): Downgrade dependencies to fix NMS

[sebathomas]

Summary

Users have reported errors starting NMS in v1.6 and v1.6.1 that seem to be due to getting incompatible versions of the DB migration dependencies.

See:
#11291
#11278
#11325

Pinning the versions of @fbcnms/platform-server and @fbcnms/sequelize-models resulted in a different error with an organizations query introduced in:
magma/fbc-js-core#108

By downgrading @fbcnms/platform-server and @fbcnms/express-middleware to a version before that change, I am able to start NMS. This will have the unfortunate side effect that organization queries are no longer case-insensitive.

Test Plan

Check out v1.6 or v1.6.1, build NMS according to the Quick Start Guide and try to log in using admin@magma.test.

Additional Information

• This change is backwards-breaking

[github-actions]

Thanks for opening a PR! 💯 Please note that all commits must be signed off. This is enforced by the DCO check.

Howto

• Reviews. The "Reviewers" listed for this PR are the Magma maintainers who will shepherd it.
• Checks. All required CI checks must pass before merge.
• Merge. Once approved and passing CI checks, use the ready2merge label to indicate the maintainers can merge your PR.

More info

Please take a moment to read through the Magma project's

• Contributing Conventions for norms around contributed code

If this is your first Magma PR, also consider reading

• Developer Onboarding for onboarding as a new Magma developer
• Development Workflow for guidance on your first pull request
• CI Checks for points of contact for failing or flaky CI checks

[sebathomas]

More details about the error:
If you don't downgrade the versions, you get the following message when you try to log into NMS:

magmalte-magmalte-1     | 2022-02-11T14:45:55.465Z [auth/express.js] error: Error getting organization Invalid value Where {
magmalte-magmalte-1     |   attribute: Fn { fn: 'lower', args: [ Col { col: 'name' } ] },
magmalte-magmalte-1     |   comparator: '=',
magmalte-magmalte-1     |   logic: Fn { fn: 'lower', args: [ 'magma-test' ] } }

This seems to be a problem with the queries introduced in magma/fbc-js-core#108, e.g.

  return await Organization.findOne({
    where: {
      name: Sequelize.where(
        Sequelize.fn('lower', Sequelize.col('name')),
        Sequelize.fn('lower', subdomain),
      ),
    },
  });

To me, it looks like there should be only one SQL lower in this query but I'm not familiar with Sequelize.

On the other hand, I don't understand why we don't see these issues on Magma master, where we use the same code.

[Neudrino]

Closing and reopening to rerun stuck CI. There were a lot of issues in March 2022.

[jheidbrink]

Approving as I can confirm that the changes resolve the described issue on my machine.

[andreilee]

Could you get yarn.lock update as well? Otherwise this looks good to me!

[jheidbrink]

I updated yarn.lock and verified again that the containers still build and dev_setup.sh succeeds.

[jheidbrink]

@andreilee Some required CircleCI checks are pending. Can you merge this anyway, given that we don't use CircleCI anyore?

[hcgatewood]

Force merging per @andreilee request